You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a user reporting a syncing problem that turned out to be our previously correct check, which is now incorrect after we introduced the Transparent history changes #1559.
After our internal discussion, we decided to remove such a check from the BlockHeight object creation.
No, we can't. The report came from the production app version.
Actual behavior + errors
java.lang.IllegalArgumentException: Height 397315 is below sapling activation height BlockHeight(value=419200)
at io.perfmark.Tag.new(SourceFile:4)
at kotlin.math.MathKt.toBlockHeight(Unknown Source:14)
at cash.z.ecc.android.sdk.block.processor.CompactBlockProcessor$Companion.access$enhanceTransaction(Unknown Source:282)
at cash.z.ecc.android.sdk.block.processor.CompactBlockProcessor$Companion$enhanceTransaction$1.invokeSuspend(Unknown Source:10)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(Unknown Source:8)
at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Unknown Source:6)
at kotlinx.coroutines.AbstractCoroutine.resumeWith(Unknown Source:22)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(Unknown Source:31)
at kotlinx.coroutines.DispatchedTask.run(Unknown Source:112)
at android.os.Handler.handleCallback(Handler.java:959)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loopOnce(Looper.java:232)
at android.os.Looper.loop(Looper.java:317)
at android.app.ActivityThread.main(ActivityThread.java:8592)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:878)
App Version: Any
Android Version: Any
Device: (if applies) Any
The text was updated successfully, but these errors were encountered:
Describe the issue
We have a user reporting a syncing problem that turned out to be our previously correct check, which is now incorrect after we introduced the Transparent history changes #1559.
After our internal discussion, we decided to remove such a check from the
BlockHeight
object creation.Can you reliably reproduce the issue?
No, we can't. The report came from the production app version.
Actual behavior + errors
The text was updated successfully, but these errors were encountered: