Ok, so I've got an app that was absolutely fine with Xcode 6.4.
But ever since upgrading to Xcode 7 I'm not able to generate GCDA files to feed into XcodeCoverage for my coverage report. To generate the files I need to set INSTRUMENT_PROGRAM_FLOW to YES. But setting it to YES causes my test run to fail. Lots of "cannot merge previous GCDA file: corrupt arc tag" entries in the console, and it then crashes in main.m showing BAD_ACCESS on the line calling UIApplicationMain.
I would really rather not use the new LLVM coverage report as it's not detailed enough.
Anyone have any ideas for this?
Related
I'm building an iOS app with FlashBuilder 4.7 and Air SDK 25.0. The app has code which installs fonts via an external SWF imported at runtime (no code in external SWF, just fonts). Imported file has been working for months but now throws below error in debugger on device :
'Uncompiled ActionsScript'
I have gone back through previous builds and some that had been working fine suddenly throw error on the swf file. Other old builds will work importing the same swf, but after running a build which fails, the working one will start throwing error!
Anyone else struck a problem like this?
I recently upgraded from SDK 22 to 25, but the problem appeared some time after that. Only significant change was running a dodgy zip ANE that crashed the debug. I've removed the ANE, but I suspect something may have been corrupted somewhere.
I've tried resetting FlashBuilder settings by deleting .metadata folder in workspace.
Tried Cleaning the projects, tried duplicating projects, tried re-publishing the swf to import.
Can't work out why some builds don't work and others do, but then stop working with no changes to the project. I feel sure there is a fix that will suddenly make all of the builds work again...
Any suggestions anyone?
I found my problem.
It appears I have previously been using only the 'Fast' packaging method to test app on ios device, which works.
When set to 'Standard' (Build) packaging to test on device it causes the swf (with embedded fonts) imported at runtime as having 'uncompiled actionscript'.
This answers my original query, but if anyone has a work-around, or alternate method of importing fonts at runtime, I'd be very happy to hear!
I'm trying to compile a project then the Xcode said that.
I hope to receive the answers for these concerns, here are the situation:
Xcode 8.3.2
Swift 3.0
All Frameworks are built via Carthage (Exclude Fabric & Crashlitics)
When I build in Debug configuration everything are ok, but when I change to configuration Release then the compile always failed.
I tried to change the Optimization Level to Fast, Single-File Optimization[-O] then the Xcode works well and I also can archive to ipa file.
I have some concerns, could you please review ?
+ How do I completely resolve this problem and keep the default Optimization Level value for configuration Release ?
+ If I change Optimization Level value to Fast, Single-File Optimization[-O], could I submit the binary file to App store review ? Does it violet Apple's tos ?
Thank you,
you can get this error when the compiler gets too confused about what's going on in your code. I noticed you have a number of what appear to be functions nested within functions. You might try commenting out some of that at a time to see if the error goes away. That way you can zero in on the problem area. You can't use breakpoints because it's a compile time error, not a run time error.
And it might be possible that you have used a custom frameworks so just remove that custom framework which shows error
I am setting up Firebase Crash Reporting on my iOS App. I have imported the necessary json files and set up the shell script. However, when I click run on the simulator, I get 11 errors all say about the same thing. Here are two of them:
warning: dump_syms: /var/folders/5l/20by_c_57fb7jhv3jh72jw9m0000gn/T/com.google.FirebaseCrashReporter.TAlixfZc/**App Name**.dSYM/Contents/Resources/DWARF/**App Name**: in compilation unit '/Users/mikelehen/firebase/firebase-client-objc/Firebase/Firebase/Utilities/FUtilities.m' (offset 0x28a2e): `
warning: dump_syms: /var/folders/5l/20by_c_57fb7jhv3jh72jw9m0000gn/T/com.google.FirebaseCrashReporter.TAlixfZc/**App name**.dSYM/Contents/Resources/DWARF/**App Name**: the DIE at offset 0x28fc1 has a DW_AT_abstract_origin attribute referring to the die at offset 0x2940f, which either was not marked as an inline, or comes later in the file `
When I try to run it on my iPhone I get only four issues.
Also, my name is not mikelehen which is for some reason in one of the issues.
After following the instructions on Firebase's website about simulating a crash, I never get the log output about the crash being uploaded.
Any idea of what I'm doing wrong here?
Edit:
Here is the script that is in my build phases:
JSON_FILE="../**App Name**/ServiceAccount.json"
GOOGLE_APP_ID=1:**App ID**
defaults write com.google.SymbolUpload version -integer 1
JSON=$(cat "${JSON_FILE}")
/usr/bin/plutil -replace "app_${GOOGLE_APP_ID//:/_}" -json "${JSON}" "$HOME/Library/Preferences/com.google.SymbolUpload.plist"
"${PODS_ROOT}"/FirebaseCrash/upload-sym
Try:
Build Phases --> Run Script
Click Run script only when installing
Those warnings are not harmful for the most part. The dump_syms utility that ships with the Cocoapod is not fully productized, so it reports errors using file names of the person who compiled it last (mikelehen in this case). We are actively looking into alternatives to dump_syms as the warnings are distracting.
As mentioned by Robert, the warnings are innocuous. Here are some suggestions that might help you out if you're having issues getting a crash to upload:
1) Make sure the debugger is not attached when you cause the crash to occur. It will intercept the exception, and nothing will get reported. So compile your program, hit stop in the debugger, manually launch the app (in either the simulator or the device), trigger the crash, then relaunch the app (without the crash so the error has time to report).
2) You should see a log message that Firebase Crash Reporting was initialized. If this is missing, make sure you've included the Firebase/Crash pod and called [FIRApp configure];.
3) Within 15 seconds, you should see another message indicating the report has been successfully sent. Be sure to wait at least 15 seconds. Reports are uploaded after a delay to avoid interfering with your app startup.
4) After the report has been uploaded, there is a delay of up to 20 minutes before data shows up in the web console.
5) If you're not using cocoapods, make sure you've added the ObjC linker flag in your Other Linker Settings in your target's build settings.
The dump_syms warnings generated are not harmful and are generated when symbol files are uploaded. So if you want to avoid warnings every time you build, you can create two targets; debug and release.
Then just disable the option of 'Run script only when installing' for Debug and enable it for release.
This will upload the symbol files.
I am trying to start testing my app, and so I enabled a new test target and a Swift file for the testing. Yet when I try to execute the testing I receive error:
IDEBundleInjection.c: Error 3587 loading bundle '/Users/fbartolom/Library/Developer/Xcode/DerivedData/inArrivoHD-ebjdiuuwdpdvchgmpsyqkpvvvyhw/Build/Products/Debug-iphonesimulator/inArrivoHD Tests.xctest
By reading some threads I also recovered the XCTest.framework from /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/ given it was not available in the selection, after locating it with find on the shell as Spotlight reported no results. Yet in so doing I got some missing symbols in the linking phase, so by reading How do I migrate from SenTestingKit/OCUnit to XCTest? I removed it.
I tried clearing the DerivedData folder several times to no avail. I also put code signing to "Don't Code signing" with changing anything.
What should I do?
I think I fixed the issue by followng the advice at:
http://dunghnt.blogspot.it/2014/12/problems-of-migrating-from-sen-test-to.html
The issue was due to incorrectly importing the MacOS test kit. Once I correctly chose the iOS one everything went in order. Perhaps a better error message would be appreciated.
I m using Xcode 4.2 and i have add AviarySDK 2.4.4 in my project.
Application runs fine in Simulator 5.0 and 4.3. I also test it on device having ios 4.1. So i want to generate .ipa file for my client. But by some reason it can not generate Archives.
It gives following error
"/usr/bin/strip -S /Applications/Projects/AppName/AppName/AviarySDK/Resources/AviarySDKResources.bundle/AviarySDKResources -o /Users/User/Library/Developer/Xcode/DerivedData/WDYWT-avjpbcnwjylobvgevipvsqttnopd/ArchiveIntermediates/WDYWT/InstallationBuildProductsLocation/Applications/WDYWT.app/AviarySDKResources.bundle/AviarySDKResources
/usr/bin/strip: for architecture armv7 object: /Applications/Projects/AppName/AppName/AviarySDK/Resources/AviarySDKResources.bundle/AviarySDKResources malformed object (unknown load command 10)
error: strip /Applications/Projects/AppName/AppName/AviarySDK/Resources/AviarySDKResources.bundle/AviarySDKResources: /usr/bin/strip exited with 1
"
Any help will really great. Many thanks in advance.
Strip errors are generally caused if you have duplicate debugging symbols in your project. Just try the following:
First Method:
Go to build settings of your project
Type Strip in the search Bar.
Under Strip Debug Symbols During Copy, you shall find Debug and under that you shall find Any SDK.
Select NO in Any SDK, select YES in Debug and select YES in Strip Debug Symbols during copy.
A little below you shall find Use Separate Strip. Select YES.
Check that Strip Style should remain All Symbols [If not then change it to that].
Second Method:
Since your error also mentions derived data, their might me duplicacy of your derived data as well. Delete Your project file from the derived data folder.
If you don't know where the derived data folder is, Google it.
I am using aviary in my current project. I have a Mac Mini and a MacAir [for work at home].
I was facing the same strip issues with aviary which I resolved using the first method mentioned above.
It took me a week to figure this out cuz i am a relative newbie in development and nothing regarding this issue has been mentioned in aviary forums as well.
PS:
MacMini: Xcode 4.5
MacAir: Xcode 4.2
Hope this helps