I had the same problem, and my solution was to make sure that the development creation profile was used to build the application.
In my case, I had two profile profiles, one for distribution and one for development. I used fastlane with a gym to build an archive. My refusal was not to indicate which profile he should use.
A crash occurred causing the gymnasium, not explicitly indicating that it was using the dev profile:
gym
The solution was to add export_method with development.
gym(export_method: 'development')
In this case, he will use the development training profile.
If you are not using fastlane, make sure that the profile you use matches the one you specified in the crashlytics beta setting.
Good luck everyone!
user4463221
source share