Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by Lineflyer
, 1 year ago
invalid pixelY coordinate 384: -144.0
via GitHub by Lineflyer
, 1 year ago
invalid pixelY coordinate 1024: -406.73785414891347
via Google Groups by emux, 10 months ago
invalid pixelY coordinate at zoom level 0: -93.80928004837207
java.lang.IllegalArgumentException: invalid pixelY coordinate 384: -144.0	at org.mapsforge.core.util.MercatorProjection.pixelYToLatitude(MercatorProjection.java:409)	at org.mapsforge.core.util.MercatorProjection.fromPixels(MercatorProjection.java:91)	at cgeo.geocaching.maps.mapsforge.v6.MfMapView.getLatitudeSpan(MfMapView.java:46)	at cgeo.geocaching.maps.mapsforge.v6.MfMapView.getViewport(MfMapView.java:34)	at cgeo.geocaching.maps.mapsforge.v6.caches.AbstractCachesOverlay.getVisibleItemsCount(AbstractCachesOverlay.java:54)	at cgeo.geocaching.maps.mapsforge.v6.caches.CachesBundle.getVisibleItemsCount(CachesBundle.java:153)	at cgeo.geocaching.maps.mapsforge.v6.NewMap.countVisibleCaches(NewMap.java:872)	at cgeo.geocaching.maps.mapsforge.v6.NewMap.calculateSubtitle(NewMap.java:852)	at cgeo.geocaching.maps.mapsforge.v6.NewMap.setSubtitle(NewMap.java:832)	at cgeo.geocaching.maps.mapsforge.v6.NewMap.access$300(NewMap.java:99)	at cgeo.geocaching.maps.mapsforge.v6.NewMap$DisplayHandler.handleMessage(NewMap.java:795)	at android.os.Handler.dispatchMessage(Handler.java:102)	at android.os.Looper.loop(Looper.java:135)	at android.app.ActivityThread.main(ActivityThread.java:5422)	at java.lang.reflect.Method.invoke(Native Method)	at java.lang.reflect.Method.invoke(Method.java:372)	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:914)	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:707)