When generating a blank iOS phonegap project I get 25 errors that say "Cross-device link".
I am guessing anyone generating a blank project will see the same thing...
Here is a screenshot for your viewing pleasure:
I have done quite a bit of searching on this but haven't come up with any solutions or clues.
I was originally creating the project to a network drive which was never an issue with past versions of phonegap but I went ahead and tried creating it locally which stopped all of the Cross-device link errors.
So I guess this is sort of a fix but it still seems like there must be a bug or something with 2.5
Update:
Shazron Abdullah from the Phonegap mailing list confirmed this and suggested that I submit a bug report.
Mailing list thread: https://groups.google.com/forum/?fromgroups=#!topic/phonegap/QhrbCwilGKo
Bug report: https://issues.apache.org/jira/browse/CB-2618
Related
I have an .epub e-book that was created in 2018. It was tested and worked with Kindle, Apple, and several other readers.
Now, the file does not work in Apple books - and multiple people have tested or complained about this.
I updated the file to make some corrections, and I still experience the error.
The exact error is: "Book Content Unavailable. There was a problem loading book content. Try closing and reopening the book or relaunching the device." (This does nothing.)
But I can take the exact same file and open it in Kindle, Nook app, and two other e-readers I downloaded from the AppStore. They read it without incident.
I created the book in Calibre and ran both the Calibre bug check and the ePubcheck plugin. No errors found.
I have no idea what the problem is, and why it is just Apple. Has anyone else encountered this? Any ideas or guesses?
Searches for similar problems from others yielded only user-related questions.
The latest version of Apple Books (corresponding to at least iOS v16.1) has a bug that has rendered certain eBooks unreadable. This seems to persist between iPad OS and iOS.
I have experienced this specifically with ePub format books created from Google Docs. One poor workaround I have found is using Pages to create the ePub version of the file - this version works, though, is without headers.
I suspect several bugs exist in the "updated" version of Books. You could try creating the ePub with a different program.
Would love if anyone has found a fix for this.
In the past I've got previous versions of the playgrounds to work. However I can't get the new 2 day old version (4.5.0) from GitHub to work.
I downloaded the zip file from https://audiokit.io/downloads/ page.
I expanded the zip.
I launched Xcode by clicking on the AudioKitPlaygrounds.xcodeproj file.
I go to the Hello World tutorial.
I click on run button and it builds successful.
No errors, nothing in console, no yellow or red build or runtime errors - but no sound. Also no sound in the handful of other playgrounds I spot tested.
I search on the internet - and found an answer saying to add this setting, but it had no effect.
AKSettings.playbackWhileMuted = true
The volume is definitely on. I have got the ROMPlayer working as a separate project using cocoa pods. But not the playgrounds. Any help much appreciated. Thanks Domc
I've resolved partly the issue - although not clear to me why this works - answer posted in case it's helpful for others.
Having tried downloading various versions, none of which worked, I tried to build many times. I noticed it seemed to be getting stuck on "Running ...." with spinning dial at top.
Researching this led me to a post re another playground with similar problem that said to untick and tick the links to the frameworks on the individual frameworks pages which I did.
A few minutes later I tried running again and I got sound! However if I select the table of contents the whole program crashes x-code and on reload you have to 'reconnect' the frameworks by ticking and unticking. [Probably this shouldn't be happening]
I am experiencing yet another weird one. After upgrading from unity 5.3.6f1 to unity 5.4.0f3 every time i open a my project it crashes(if the substance is not included it doesnt crash only when i build the project). it then breaks the substance, they are stuck in generating state. After fixing the substance and then building the project for iOS platform the crash happens during the build process and the substance breaks in the build, in other words the substance is completely broken and all references are missing. i created a unlisted video here that you can see what i mean, Check out the video here Crazy right?
I've tried reproducing the error with a new project but it works fine when i build. so I'm wondering if it hasn't got anything to do with actually upgrading from the previous version.
Can anyone share any light on this?
Thanks in advance
P.S. here is the code it spits out just before it breaks the substance.
material->IsFlagEnabled (ProceduralMaterial::Flag_Clone) || m_PingedMaterial == NULL || m_PingedMaterial == material
UnityEditor.DockArea:OnGUI()
It turned out that this was a bug. and the Allegorithmic team and Unity team got it fixed so quickly. The version with the fix is Unity 5.5b6, I've tested it and it works 100%
Substance: Fixed crash when selecting a ProceduralMaterial after switching build platform. (820301)
Substance: Fixed occasional ProceduralMaterial asset import crash. (822217)
Substance: Fixed SubstanceImporter.ExportBitmaps generated file names.
Trying to integrate my app with Facebook for login proposes, i've happened to notice the following log line:
2014-01-07 15:22:08.843 Nutrino[7457:70b] FBSDKLog: The FacebookSDKResources.bundle is no longer required for your application. It can be removed. After fixing this, you will need to Clean the project and then reset your simulator.
The problem is FacebookSDKResources.bundle is not even existing in my FacebookSDK directory. So basically this log message is redundant for me.
Normally i won't care much, but this log message is popping into my log console 3 times in a raw each time i'm instantiating FBLoginView.
Been looking around and saw this answer which state that the guy is probably getting this error after having upgraded to a newer version of Facebook SDK. Unfortunately i'm not upgrading. I started a new project from scratch so i don't have any reference to safely remove from the app project.
Any suggestions? How can i get rid of these annoying log messages
Thanks in advance.
Gil
UPDATE
Ok - I've found out the source of the problem!!
I'm developing my app in xCode5.. Once in a while I open an older version of xCode with an older version of the app for some code references, so the problem happens when both projects are opened simultaneously.
The FacebookSDKResources.bundle does exists on the older version of the project and this is the cause!
Hope it'll helps someone.
original answer
I'm not really sure if this is what solved it, since I left it as it was for a while and the next time I checked those log messages weren't there, but the only thing I do remember changing was the fact the I made my FBLoginView instance a singleton, so there was only one instance of it.
Worth the shot if anyone is dealing with the same issue.
apologies for cluttering up stackoverflow with what is clearly a trigger.io support request.
I've created 2 native modules, and uploaded multiple versions of each. However, when I try to add one of these 'private modules' to one of my trigger.io apps via the Toolkit.app, I get an error 'You cannot activate this module as it has no uploaded versions.' - which is clearly not the case.
anybody have any insight on why this error is happening?
or more to the point are there any trigger.io staff on SO who can get this fixed / or explain to me where I might be going wrong?
This is a bug in how we're comparing versions in the 3.3.62 version of the Toolkit - we'll be deploying a new version with a fix later today.
Sorry for the inconvenience!