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.
Firebase Crashlytics : Host name may not be empty
See original GitHub issue[REQUIRED] Step 2: Describe your environment
- Android Studio version: 4.0
- Firebase Component: firebase-crashlytics
- Component version: 17.0.1
[REQUIRED] Step 3: Describe the problem
On building signed apk, i am getting Host name may not be empty error
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Host name may not be empty - Stack Overflow
This issue is caused due to empty xml file in your res directory. Open the res directory in explorer/finder ...
Read more >[Solved]-Host name may not be empty-kotlin - appsloveworld
This issue is caused due to empty xml file in your res directory. Open the res directory in explorer/finder sort all the xml...
Read more >Admin Authentication API Errors | Firebase - Google
The error message should contain the response from the Authentication ... used to authenticate the Admin SDKs cannot be used to perform the...
Read more >Crashlytics在上传deobs文件时出现问题 - 腾讯云
IllegalArgumentException : Host name may not be empty at com.crashlytics.reloc.org.apache.http.util.Args.containsNoBlanks(Args.java:84) at ...
Read more >New features in Android Studio Preview
Live Edit; SDK insights; App Quality Insights from Firebase Crashlytics ... If you're not using Crashlytics yet and would like to learn more...
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
@damionx7, With the update of AS 4.0, below proxy setting lines recommended to be added in gradle.properties:
systemProp.http.proxyHost= systsemProp.http.proxyPort=80 systemProp.https.proxyHost= systemProp.https.proxyPort=80Removing these lines fixed the issue for me.
Thanks, I solved the issue by doing as @akndmr suggested. One thing to note it that you will have to delete these lines from ~/.gradle/gradle.properties in your User directory