So, it doesn't seem to be a code problem.įurthermore, if you look at the stack trace, there is nothing pointing to our project. However, I can't emphasize enough that if I just run the app (play button, ^R) and run it on the very same device, it works just fine! Log in with no problem.
Restart Android Studio! (turn it off and on again)Īnd so far, nothing works.Ok, I've been adding breakpoints all over to see how things work, so who knows? There's some merit there.Here are the things I've tried to fix it: Process:, PID: 2399Īt .AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:1991)Īt .AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2025)Īt .take(LinkedBlockingQueue.java:410)Īt .getTask(ThreadPoolExecutor.java:1035)Īt .runWorker(ThreadPoolExecutor.java:1097)Īt $n(ThreadPoolExecutor.java:588) I can get to the login screen, but the app would always crash at the same point in the middle of the authentication.
The user must then authenticate with a username/password which calls out to an external service. Of course, I've been making changes all day, hence the "it seems" above.
Then after lunch it began failing 100% of the time. To clarify, I was running the debugger all morning without incident (apart from the occasional glitch or crash).
25.0.3 (December 16, 2016) Fixed fastboot bug causing Android Things devices to fail to flash 25.0.2 (December 12, 2016) Updated with the Android N MR1 Stable release (API 25) 25.0.1 (November 22, 2016) Updated with the release of Android N MR1 Developer Preview 2 release (API 25) 25.0.0 (October 19. The funny thing is, if I ran the app normally it would work just fine. Fixed Systrace command line capture on Mac. While working today, it seemed as if suddenly I could no longer debug our application.