automate-symbolication: Option to fail silently?
See original GitHub issueI’m trying to use automate-symbolication
, or automatically uploading source maps for a react native project. However, looks like failing to upload to bugsnag (due to timeouts or spotty internet) is causing the entire build step to fail.
I would like to know, or request, if it would be possible to only upload source maps if a “production” build is being generated (that is, for iOS only do this when archiving, and for Android only when running ./gradlew bundleProdRelease
). Otherwise, this is very inconvenient since installing “production” builds into the device directly from XCode or ADB will also trigger a source map upload.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How to handle errors with grace: failing silently is not an option
The first step of handling errors is to identify when an “error” is not an “error!”. This of course depends on your application's...
Read more >Provide option to fail silently. · Issue #1293 · stedolan/jq - GitHub
I'm using jq inside of a shell script where it is part of a command pipeline. It is looking for an item in...
Read more >Is there a way to make "mv" fail silently? - Unix StackExchange
— GNU's mv has nice "destination first" option ( -t ) and xargs can skip running its command if there's no input at...
Read more >ThreadPool Tasks Fail Silently (and how to fix it)
Asynchronous tasks issued to the ThreadPool can fail silently. ... This can be achieved by setting the error_callback argument to the name ......
Read more >Method that fails loudly vs silently - Stack Overflow
So, I have two questions: Does it sound as a good idea to create two API endpoints instead of one?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It says it is a “retired document”, but I guess the info is still valid. Anyways, with your first response I believe I got it to work as expected now. Thanks!
Hey @cristianoccazinsp,
These are environment variables which are generated by Xcode when you run a build. They can be accessed by the build phase scripts at build-time which will allow you to know what kind of build is happening. If
ACTION
is equal tobuild
, it’s a debug or release build, if it’s set toinstall
it’s building for an archive.Unfortunately, there’s no particularly good reference for these environment variables from Apple as far as I know – other than this resource, which gives some examples for each of the exported environment variables.
You can output all of your environment variables in a build by adding a simple build phase script as follows to your Xcode build phases if you want to test out what the env variables look like for different build types:
bugsnag.uploadReactNativeMappings = false
switches the JS sourcemap upload off.bugsnag.enabled = false
switches the whole plugin off, including source map uploading.I’d recommend that you do set
enabled
tofalse
for variants that you don’t want Bugsnag to run on, just so that you don’t have any assets uploading needlessly.