Bugsnag build phase script to auto upload dsym with Xcode 14 failed to upload

[halvi00]

Bugsnag build phase script to auto upload dsym with Xcode 14 failed to upload

[johnkiely1]

Hi @halvi00. Have you double checked you have added the correct api key for your project you expect? Are you seeing any Bugsnag related warmings/messages in the logs? Are you able to share your version of the build script? Feel free to write in to [email protected] if you don't want to share this information publicly.

[halvi00]

Hi @johnkiely1 , Yes I'm using the same api key to upload manually using bugsnag-dsym-upload where the dsyms are getting uploaded.
I'm not seeing any bugsnag related warnings.
My build version is 1.0 . Do you want my manual script as well?

I'm using this script. adding-a-build-phase-manually

[halvi00]

Hey @johnkiely1 , any update on this?

[matthewjhowells]

Hi @halvi00. We can’t see any reason why the custom build script provided in the docs wouldn’t work. Can you confirm that you have followed all of the steps provided in the documentation?

Did you follow step 5 from the instructions to add the dsym path to the input files list?

Do you have the ENABLE_USER_SCRIPT_SANDBOXING build setting enabled in your project?

Would you be able to share a screenshot of your custom build phase? If you would rather not share this publicly, you could write directly to the Bugsnag Support team ([email protected]), providing a link to this GitHub issue along with your screenshot.

[halvi00]

Hi @matth-bugsnag

I am using the same script as provided in the docs. And yes I have followed all the steps.
I had not enabled ENABLE_USER_SCRIPT_SANDBOXING. Since I didn't need it. But I tried enabling it and it still won't work.

I have started getting this error now:

cannot read /Users/**/Library/Developer/Xcode/DerivedData/bar-mobile-abiwryjtdnwesrechlnbvllrvdhp/Build/Intermediates.noindex/ArchiveIntermediates/bar-mobile (iOS)/BuildProductsPath/Release-iphoneos/bar-mobile.app.dSYM/Contents/Resources/DWARF/bar-mobile (iOS)

Im attaching the ss here. I have added the api key as well. Just not showing in the screenshot.

[matthewjhowells]

Hi @halvi00.,

The error you have started seeing is coming from lines 9 - 13 of the custom build script; You wouldn’t have seen this before enabling ENABLE_USER_SCRIPT_SANDBOXING as lines 4 - 14 of the build script are not run when ENABLE_USER_SCRIPT_SANDBOXING is disabled.

Its worth saying that if you are not already using ENABLE_USER_SCRIPT_SANDBOXING, we do not recommend enabling it.

While normally you would not have seen this error, it does suggest that the path being generated in the script (using Xcode environment variables; see line 16 of the script) does not lead to a valid DYSM file.

Have you changed any Xcode settings from their defaults? (e.g. the Derived Data or Archives paths).

Can you provide a path for the directory your dSYM files are outputted / archived in (i.e. what path do you use when using bugsnag-dsym-upload in the terminal)?

Does the beginning of this path match with your DWARF_DYSM_FOLDER_PATH Xcode environment variable?

Feel free to omit any personal information from these paths.

[halvi00]

Hi @matth-bugsnag

Yes I started seeing this error after using ENABLE_USER_SCRIPT_SANDBOXING. I don't need it, so I have disabled it.

The path for the directory of dSYM that I use for uploading: (I drag drop the dSYM folder from archived folder)

/Users/hira/Library/Developer/Xcode/Archives/2023-01-03/barglance-mobile\ (iOS)\ 1-3-23,\ 12.09\ PM.xcarchive/dSYMs

I don't see any environment variable set for DWARF_DYSM_FOLDER_PATH or DWARF_DSYM_FILE_NAME under arguments tab from build scheme. Shouldn't this be set by default?

Also haven't changed any Xcode settings from their defaults.

[matthewjhowells]

Hi @halvi00,

Yes those environment variables are set by default. There are a couple of ways that you can see them.

If you build your project in the terminal using the xcodebuild command you can add -showBuildSettings to the end of your command to have it print a copy of your environment variables to the terminal.

Alternatively, if you use the Xcode applications build functions, you could add the following three lines to the start of your custom build script, and view the output in the Report Navigators build logs:

puts "#{ENV['DWARF_DSYM_FOLDER_PATH']}"
puts "#{ENV['DWARF_DSYM_FILE_NAME']}"
puts "#{ENV['TARGET_NAME']}"

Would you be able to share the output of these environment variables with us?

Could you also share the full path to your projects dSYM output directory immediately following a build?

If you have not modified your Xcode settings then your dSYM output directory should be something like the following: /Users/<USER_DIRECTORY>/Library/Developer/Xcode/DerivedData/IOS-Test-App-ecuvqxmjzjaarxflvuffvsvhhgga/Build/Products/Release-iphonesimulator/IOS-Test-App.app.dSYM/Contents/Resources/DWARF

With these details, we can compare what the script expects and what is provided in the environment variables. This will allow us to check whether the build script might require modifications to access your dSYMs directory at build time.

[halvi00]

Hi @matth-bugsnag ,

Using Xcode application build function, I was unable to see any output after adding this in custom build script :
puts "#{ENV['DWARF_DSYM_FOLDER_PATH']}"

However running xcodebuild command in terminal gave the following output:

DWARF_DSYM_FOLDER_PATH = /Users/<USER_DIRECTORY>/Library/Developer/Xcode/DerivedData/barglance-mobile-abiwryjtdnwesrndifncidnwp/Build/Products/Release-iphoneos

DWARF_DSYM_FILE_NAME = barglance-mobile.app.dSYM

TARGET_NAME = barglance-mobile (iOS)

After building the app in simulator, this is the directory of dSYM folder:
Note: This app is still in development phase.

/Users/<USER_DIRECTORY>/Library/Developer/Xcode/DerivedData/barglance-mobile-abiwryjtdnwesrndifncidnwp/Build/Products/Debug-iphonesimulator/barglance-mobile.app.dSYM/Contents/Resources/DWARF

[halvi00]

Hi @matth-bugsnag, any update on this?

[matthewjhowells]

Hi @halvi00,

Based on the directory paths you have provided we would expect the dSYM upload script to work as intended. Through our testing, and while trying to replicate your environment as closely as possible (Similar file paths, same Xcode version and build script), we have not be able to reproduce what you are experiencing.

The dSYM script finds sourcemaps based on build time environment variables and wildcard usage (*) , which means that if a dSYM has been generated by Xcode, the BugSnag dSYM uploader script should be able to find and upload them using the scripts curl request.

Given this, it may be worth reviewing your Xcode preferences and build settings, as the problems you are seeing potentially stem from the build not producing or outputting dSYM files as we would expect.

In the meantime we would recommend continuing to use the bugsnag-dsym-upload tool to upload your sourcemaps. I appreciate that this does not solve your problem, however, from our end (based on the information we have been provided) we cannot see any reason why the dSYM files should not be getting uploaded.

[johnkiely1]

Going to close this out as we haven't heard back from you in a while and as mentioned above theres not a lot more we can do from our side. We suspect it will likely be an environmental issue which is very difficult for us to debug.