-
Notifications
You must be signed in to change notification settings - Fork 138
-
Notifications
You must be signed in to change notification settings - Fork 138
Gastly crashes GoIV #135
Comments
Can confirm. Does the same for me. I see it happen when the smoke around it covers the CP number on the top of the screen. If it the CP is clearly visible, it works just fine and I didn't see this issue in the older version of GoIV as well. |
Are you running 2.1.0 or github version? |
It's 2.1.0. How do I compile master to make an apk? I am sorry I've never On 22 Aug 2016 4:00 p.m., "nahojjjen" notifications@github.com wrote:
|
Tried the github version, and looks like it's been fixed for similar cases as well (Koffing, Weezing, etc). Thanks! |
By the way, if you are in a Pokemon screen, scroll up the page (so that the CP goes out of scope) and press the IV button, it disappears and when you stop the service it crashes as it did with the Gastly problem. |
Confirmed problem in 2.2.0 version with latest commit "Adjust Arc": when screen scrolled up - IV button disappears, nothing happens and when GoIV is closed, following error occures:
Error is here:
Seems like arcPointer is not attached to windowManager that's why |
@jehy I'm working on that crash, I have identified something iffy which might cause it in part. |
`infoShown` does not reflect correctly whether the `infoLayout` and `arcPointer` were added or not; `infoShownReceived` is closer but is cleared if `batterySaver`. In particular, if the main activity hasn't replied yet to the request to OCR the pokemon, then `infoShown` is true, while `infoShownReceived` isn't true yet and `infoLayout` and `arcPointer` aren't shown, causing the crash. This causes at least a race condition that this PR fixes. This is the crash shown as `farkam135#3` and `farkam135#33` in Crashlytics. https://www.fabric.io/goiv/android/apps/com.kamron.pogoiv/issues/57bc2435ffcdc042501dbfa7 https://www.fabric.io/goiv/android/apps/com.kamron.pogoiv/issues/57b57b39ffcdc04250dc0403 Now, not only we have a race condition here, but sometimes the main activity never replies, making this bug *much* easier to hit. Next commit fixes that, too.
Fix farkam135#135, part 2. This simply ensure that we answer back with an intent even when we found no pokemon, so that we reset the state of the various state flags used by `Pokefly` and `MainActivity`.
Use `try...finally` to ensure we answer with an intent no matter what. ALso for farkam135#135.
`infoShown` does not reflect correctly whether the `infoLayout` and `arcPointer` were added or not; `infoShownReceived` is closer but is cleared if `batterySaver`. In particular, if the main activity hasn't replied yet to the request to OCR the pokemon, then `infoShown` is true, while `infoShownReceived` isn't true yet and `infoLayout` and `arcPointer` aren't shown, causing the crash. This causes at least a race condition that this PR fixes. This is the crash shown as `farkam135#3` and `farkam135#33` in Crashlytics. https://www.fabric.io/goiv/android/apps/com.kamron.pogoiv/issues/57bc2435ffcdc042501dbfa7 https://www.fabric.io/goiv/android/apps/com.kamron.pogoiv/issues/57b57b39ffcdc04250dc0403 Now, not only we have a race condition here, but sometimes the main activity never replies, making this bug *much* easier to hit. Next commit fixes that, too.
Fix farkam135#135, part 2. This simply ensure that we answer back with an intent even when we found no pokemon, so that we reset the state of the various state flags used by `Pokefly` and `MainActivity`.
Use `try...finally` to ensure we answer with an intent no matter what. ALso for farkam135#135.
Samsung Note 5, 6.0.1, GoIV 2.1.0. It didn't happen with the last version from the Play Store, it would just fail to recognize the CP when the smoke covered it.
The text was updated successfully, but these errors were encountered: