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

How to disable crash reporting for TestFlight? #31

Closed
cheenu opened this issue Apr 6, 2014 · 3 comments
Closed

How to disable crash reporting for TestFlight? #31

cheenu opened this issue Apr 6, 2014 · 3 comments

Comments

@cheenu
Copy link

cheenu commented Apr 6, 2014

It looks like this gem generates the initialization code into testflight_launcher.rb which is generated every time rake is run.

So I'm unable to add any code to this file e.g. TestFlight.setOptions(...)

How do I add this code? Is the testflight_launcher.rb code run before or after didFinishLaunchingWithOptions?

@christos
Copy link

christos commented Apr 7, 2014

Hello @cheenu

As you might have guessed, testflight_launcher.rb is indeed loaded before didFinishLaunchingWithOptions is called. The Ruby code in testflight_launcher.rb is evaluated when the file is loaded, as it is inline in the file.

Unfortunately this means takeOff is called before you get a chance to set any options, which you must do before calling takeOff

Caveat emptor

@cheenu
Copy link
Author

cheenu commented Apr 7, 2014

Hi @christos

Thanks for the reply with the clarification! Looks like the only option then is monkey patching the create_launcher method to manually add the options I need.

Closing this issue but hopefully someone who's more experienced than me implements an elegant way to set options in motion-testflight. 😃

@cheenu cheenu closed this as completed Apr 7, 2014
@markrickert
Copy link

Hey guys, also make sure to be using @hboon's fork that only calls TestFlight.takeOff once per load instead of every time the app enters the foreground. See #27 for reference and how to put it in your gemfile.

@Watson1978 any chance of getting this merged into master and a new version of the gem released to fix this issue?

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

3 participants