Closed gmale closed 5 years ago
TODO: Be more resilient against this error:
Process: cash.z.android.wallet.testnet, PID: 3470 02-22 03:08:19.827 E/AndroidRuntime( 3470): io.grpc.StatusRuntimeException: UNKNOWN: context deadline exceeded 02-22 03:08:19.827 E/AndroidRuntime( 3470): at io.grpc.Status.asRuntimeException(Status.java:530) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at io.grpc.stub.ClientCalls$BlockingResponseStream.hasNext(ClientCalls.java:576) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at cash.z.wallet.sdk.data.CompactBlockStream$Connection.checkNextBlock(CompactBlockStream.kt:196) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at cash.z.wallet.sdk.data.CompactBlockStream$Connection.access$checkNextBlock(CompactBlockStream.kt:81) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at cash.z.wallet.sdk.data.CompactBlockStream$Connection$loadBlockRange$2.invokeSuspend(CompactBlockStream.kt:181) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:32) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:233) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:594) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at kotlinx.coroutines.scheduling.CoroutineScheduler.access$runSafely(CoroutineScheduler.kt:60) 02-22 03:08:19.827 E/AndroidRuntime( 3470): at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:742) 02-22 03:08:19.834 W/ActivityManager( 1885): Force finishing activity cash.z.android.wallet.testnet/cash.z.android.wallet.ui.activity.MainActivity
If I navigate to any screen and then back to the home screen (either using the top left arrow or the device back button), the loading and intro screens appear.
The lock animation on the first informational into screen feels like it ends too early. The lock appears, opens, and then snaps shut, but that final animation feels like a glitch rather than intentional.
Nearly everything is fixed. The remaining items have been migrated to #13
Known/Discovered issues:
Migrated from #11 :