I updated my Flash Builder SDK to use the latest AirSDK 15,change the application to use 15.
After that I got the error: Could not resolve
<s:ViewNavigatorApplication>
I the found some one else had that problem and added the /frameworks/libs/mobile to the build path I added the path and then i got a different error: Could not resolve
<s:Callresponder>
I then tried to add the MX path and a lot of other paths but could not get rid of the error. I have now spend over 10 hours all because I need to update my iOS application so it will run on the new iOS8.
Flash Builder 4.6 Premium - Mac OS Maverick.
Thanks.
Adding
-swf-version=26
--namespace+=http://ns.adobe.com/mxml/2009,${flexlib}/mxml-2009-manifest.xml
--namespace+=http://www.adobe.com/2006/mxml,${flexlib}/mxml-manifest.xml
--namespace+=library://ns.adobe.com/flex/spark,${flexlib}/spark-manifest.xml
to the "Additional compiler arguments" in properties -> Flex Compiler seems to fix it.
Related
I have a slight issue when build my Xcode project, get tones of warning after update pod. It looks like this
Already search the whole site here but still no luck. it doesn't affect the project but it is quite annoying. Anyone could help?
It probably means their binary file has non-aligned pointer when they compile their code. In those cases the alignment basically defaults to 1 byte and hypothetically might impact performance.
After updating to Xcode 8.3 public release I am still seeing this error, so Google might need to compile their static library with different settings to make it go away.
Got this response from firebase support:
This is a known issue with Xcode 8.3 beta, so it might be a beta thing
and Xcode being extra verbose. It works well though with 8.2.1 so I
recommend temporarily use it to avoid the warnings or ignore the
warnings on 8.3 beta if it does not affect your app.
This has been fixed in Firebase 3.16.0 (Firebase Core 3.6 + Firebase Analytics 3.8.0)
guys, it is all fixed now. Tested it all myself on two projects. You got to go to the correct directory of your project so that your pod spec file is visible to your command line commands, run
pod update
and see it all fixed and working properly!
These problems are addressed, and likely fixed, with release 3.16.0.
I have a slight issue when build my Xcode project, get tones of warning after update pod. It looks like this
Already search the whole site here but still no luck. it doesn't affect the project but it is quite annoying. Anyone could help?
It probably means their binary file has non-aligned pointer when they compile their code. In those cases the alignment basically defaults to 1 byte and hypothetically might impact performance.
After updating to Xcode 8.3 public release I am still seeing this error, so Google might need to compile their static library with different settings to make it go away.
Got this response from firebase support:
This is a known issue with Xcode 8.3 beta, so it might be a beta thing
and Xcode being extra verbose. It works well though with 8.2.1 so I
recommend temporarily use it to avoid the warnings or ignore the
warnings on 8.3 beta if it does not affect your app.
This has been fixed in Firebase 3.16.0 (Firebase Core 3.6 + Firebase Analytics 3.8.0)
guys, it is all fixed now. Tested it all myself on two projects. You got to go to the correct directory of your project so that your pod spec file is visible to your command line commands, run
pod update
and see it all fixed and working properly!
These problems are addressed, and likely fixed, with release 3.16.0.
Hi after I've updated my mac to OS X 10.10(Yosemite) my project won't compile now. :(
I've tried to delete derivedata but still the problem occurs.
Here's the error
/Users/ronpelayo/loke/Boogiespot-iOS-Library/BoogieLibrary/BoogieSpot.xcdatamodeld: Compilation failed for data model at path '/Users/ronpelayo/Library/Developer/Xcode/DerivedData/BoogieLibrary-ddzzhhrbirmakmgvaskpalwekowx/Build/Products/Debug-iphoneos/BoogieSpot.momd/BoogieSpot 10.mom'
and here's the screenshot of my xcdatamodeId
I hope someone can help me with my problem I don't know what to do now :(
It appears that the problem is within OS X 10.10(Yosemite)
http://openradar.appspot.com/radar?id=6385584100605952
I've tried to compile my project in Xcode 6.1 and it's running now but I'm still investiging if it has bugs.
So, i'm loading an old project to do some updates. The project has been upgraded a few times in the past without issue. However, upgrading to 11.5 is producing the dreaded error: A Fatal Error Has Occurred. Click OK to Quit.
The next screen produces MS C++ Runtime Error:
Runtime Error!
The app has ... terminated in unusual way... Please contact support team ...
Completely useless error so i'm wondering if anyone has discovered common causes. This project does have an old 3rd party Xtra called MasterApp. However, all the other casts and .dir files upgrade fine when using this Xtra. The only thing unique about the files that fail is they are both over 200mb.
since the error message of director does not help, I would suggest you to try these things to narrow the error:
-Open the files in Director 10 an copy all Cast Members etc into a new file. Try if that helped.
-Remove the xtra fro the files and see if that helps. If it helps, than try to replace - for example by the BudApi-Xtra.
-Does your casts have big media which are not images? Sounds oder Videos for example? I would suggest lokking at them first.
-Try to convert the files on a windows PC.
BTW: Do you have the latest version of D11.5? MayBe there is an update that you can install.
Regards
Arno
My project was working without errors on XCode 4.2 on Lion. Now I'm running Mountain Lion with XCode 4.4 and when I try to build the project it gives me an error that tree.h file cannot be found. I checked the header search path and it was correct. I searched the web for such an error and found the same solution on many different pages but couldn't understand that particular solution, see for example this page.
How can I solve this problem? Alternately, can you clarify the weird solution that is spread all over the internet?
I had to add another header search path which is: $(SDKROOT)/usr/include/libxml2. This fixed the problem.
Go in the XCode preferences and install the command line tools.