Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue on the final step of the process. #1

Open
cgascons opened this issue Feb 28, 2014 · 7 comments
Open

Issue on the final step of the process. #1

cgascons opened this issue Feb 28, 2014 · 7 comments

Comments

@cgascons
Copy link

Hi Alexis & FreshPlanet's team.

First of all, let me start by thanking you for sharing this ANE with the world, I really appreciate it. I've been trying to use it though and I found an issue I can't seem to find a solution to.

The issue is related to the final step of the whole process (running the script). My problem is that I can't seem to find any .dSYM file on my computer, I've tried with a Mac and a PC, and got no luck so far. I believe this issue is related to my Flash Builder version (4.6). That version doesn't have the "keep bin-release-temp" folder you say, so I can't manage to get that file from anywhere. I've even tried to uncompress manually the .ipa file (getting the Payload folder with the .app file inside), and even checking the contents of that app I couldn't find the file required for running the script. Is there anything I could do to get to that file?

Thank you again for the help!

@ataugeron
Copy link
Contributor

I've been using FB 4.7 for a while so I'm not 100% sure, but I think you
need to package your app with ADT to have the dSYM.

Also, you may want to look at item 10 at
https://blogs.adobe.com/airodynamics/2012/06/11/common-issues-faced-in-developing-native-extensions-for-air-on-ios
.

On Fri, Feb 28, 2014 at 8:31 AM, cgascons [email protected] wrote:

Hi Alexis & FreshPlanet's team.

First of all, let me start by thanking you for sharing this ANE with the
world, I really appreciate it. I've been trying to use it though and I
found an issue I can't seem to find a solution to.

The issue is related to the final step of the whole process (running the
script). My problem is that I can't seem to find any .dSYM file on my
computer, I've tried with a Mac and a PC, and got no luck so far. I believe
this issue is related to my Flash Builder version (4.6). That version
doesn't have the "keep bin-release-temp" folder you say, so I can't manage
to get that file from anywhere. I've even tried to uncompress manually the
.ipa file (getting the Payload folder with the .app file inside), and even
checking the contents of that app I couldn't find the file required for
running the script. Is there anything I could do to get to that file?

Thank you again for the help!

Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

@cgascons
Copy link
Author

Hi again, thanks for the quick response,

I actually did read that blog before and made sure to follow those steps, but the dsymutil tool was already located at its intended place (actually it was in both locations). I will try to package the app with ADT and, if that doesn't work I guess I'll just have to upgrade to 4.7 :(

Thanks again for the help Alexis!

@flex01
Copy link

flex01 commented Mar 12, 2014

Hi Alexis,
I was also facing the same issue, while using FB 4.6 as there is no option for "keep temp release", then i moved to FB 4.7, but this also did not generate the .dsym file. So i followed the instruction to copy the dsymutil file at /user/bin folder manually. Now FB 4.7 generates the .dsym folder inside 'temp-release-folder'.

When i follow the next instruction to execute the run.sh command i get an error "command not found". My current directory at terminal is tools while executing the run.sh command. Might be i am doing something wrong here. Can you please explain the following command which you have mentioned inside the Crashlytic ane document.

cd /path/to/the/ane
tools/run.sh CRASHLYTICS_API_KEY PATH_TO_IPA PATH_TO_DSYM

Thanks

@ataugeron
Copy link
Contributor

If you are in the tools folder, then ./run.sh should work. If it doesn't, make sure the file is executable with chmod +x run.sh.

@flex01
Copy link

flex01 commented Mar 18, 2014

Hi Alex,
Thanks for your response.

run command is working now, but i have felt into another issue:-

could not stat active Xcode path '/Volumes/Xcode/Xcode.app/Contents/Developer'. (No such file or directory)

xcodebuild[3252:1007] [MT] PluginLoading: Required plug-in compatibility UUID 37B30044-3B14-46BA-ABAA-F01000C27B63 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/KSImageNamed.xcplugin' not present in DVTPlugInCompatibilityUUIDs
** BUILD FAILED **

The following build commands failed:
PhaseScriptExecution Run\ Script build/dsymupload.build/Release/dsymupload.build/Script-398BD51C1876C966003AAA43.sh

I searched for the same issue and found a solution to add the following entry to info.plist file.

DVTPlugInCompatibilityUUIDs

37B30044-3B14-46BA-ABAA-F01000C27B63

As we don't have direct access to .plist file with AIR so i added the same to application-app.xml file, but this did not solve the issue, can you please help me on this.

Thanks

@fu-iq12
Copy link

fu-iq12 commented Mar 18, 2014

I've used the above tips and the run.sh succeeds, the app was discovered by Crashlytics but I don't get any crash report.

I'm packaging with Air13 beta (command line), also tried flex4.6 + Air13. Does anyone get crash reports while packaging with Air13?

[Update]
it works in ios-test-interpreter or ios-debug-interpreter modes, but doesn't in ios-ah-hoc (using -useLegacyAOT no doesn't help).
Any idea?

@wman1980
Copy link

We also have that problem:
The following build commands failed:
PhaseScriptExecution Run\ Script build/dsymupload.build/Release/dsymupload.build/Script-398BD51C1876C966003AAA43.sh

Any idea whats the problem?

UPDATE:
We fixed the problem by running the shell script with "-v" Option.
Currently the shell script looks for Crashlytics Framework under "../ios/Crashlytics.framework", but actually the framework resides in "../ios/Frameworks/Crashlytics.framework". All we needed to do is to move that framework one folder up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants