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.
java.lang.IllegalArgumentException: width and height must be > 0 error line at onDestroy
See original GitHub issuejava.lang.IllegalArgumentException: width and height must be > 0 on Activity onDestroy method
Is there anything I am missing?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
IllegalArgumentException: width and height must be > 0 while ...
java.lang.IllegalArgumentException: width and height must be > 0 is because in your Bitmap.createBitmap() call v.getLayoutParams().width or ...
Read more >[Solved] How to fix Crashlytics "width and height must be > 0 ...
The problem happens because xpnl_circlebackground size is zero or less. It can happen for example if the view is anchored to both sides...
Read more >java.lang.IllegalArgumentException: Width and ... - YouTrack
java.lang.IllegalArgumentException: Width and height must be >= 0 at java.desktop/java.awt.Component.getBaseline( Component.java:2938 ) ...
Read more >Activity - Android Developers
The entire lifetime of an activity happens between the first call to onCreate(Bundle) through to a single final call to onDestroy() . An...
Read more >graphics/java/android/graphics/Bitmap.java - Google Git
import java.io. ... throw new RuntimeException("internal error: native bitmap is 0"); ... throw new IllegalArgumentException("height must be > 0");.
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
Your assumption is right. A possible fix would be using a color drawable instead:
Original issue has been resolved.