Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Fabric] failed to download settings Error Domain=FABNetworkError Code=-5 "(null)"
See original GitHub issueStarted seeing the following error recently:
[Fabric] failed to download settings Error Domain=FABNetworkError Code=-5 "(null)" UserInfo={status_code=403, type=2, request_id=a3bfa6de489702b7b491a71b1138afd0, content_type=application/json; charset=utf-8}
Could you give a hint on what I could be doing wrong?
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Fabric failed to download settings Error Domain ...
When I build and run my app in release it installs but never starts running from xcode. stopping with [Fabric] failed to download...
Read more >[Solved]-Fabric failed to download settings Error Domain ...
Coding example for the question Fabric failed to download settings Error Domain=FABNetworkError Code=-5.
Read more >Failed to download settings Error Domain ... - GitHub
Researching I found a lot of related problems to the fabric implementation, but fabric is not connected to the project. Do you have...
Read more >Failed to download settings Error Domain=FABNetworkError ...
I succeeded in building but the error of the title [Fabric] failed to download settings Error Domain=FABNetworkError Code=-5 "(null)" ...
Read more >iOS : Fabric failed to download settings Error ... - YouTube
iOS : Fabric failed to download settings Error Domain=FABNetworkError Code=-5 [ Beautify Your Computer ...
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 Free
Top 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
So finally found the issue. The warning above turned out to not affect the report send-out. The reason we didn’t see the report in Firebase Crashlytics was that we had a wrong bundle identifier in project.pbxproj. It has to be the same as the one in GoogleService-Info.plist which is what you registered your Firebase app with.
I’ll give it a try. Will post the solution here (hopefully 🙂). Thanks for looking anyway @jaumard !