Bugs

Always crashing on Android 16 upon clicking on the submit button. The crash happens with the Android SDK 17.1.4 and 17.1.3 - had to downgrade back to 17.1.2 to avoid it. Here's the stacktrace: java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0 at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) at jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266) at java.util.Objects.checkIndex(Objects.java:385) at java.util.ArrayList.remove(ArrayList.java:558) at com.shakebugs.shake.internal.domain.models.ActivityHistory.addTouchEvent(SourceFile:2) at com.shakebugs.shake.internal.j8.a(SourceFile:69) at com.shakebugs.shake.internal.j8.a(SourceFile:3) at com.shakebugs.shake.internal.w4.v(SourceFile:4) at com.shakebugs.shake.internal.v4.a(SourceFile:10) at com.shakebugs.shake.internal.v4.$r8$lambda$6twZSQiexMSdShLXQT5FZZnFBhE(Unknown Source:0) at com.shakebugs.shake.internal.v4$$ExternalSyntheticLambda7.onClick(D8$$SyntheticClass:0) at android.view.View.performClick(View.java:8228) at com.google.android.material.button.MaterialButton.performClick(MaterialButton.java:1218) at android.view.View.performClickInternal(View.java:8205) at android.view.View.-$$Nest$mperformClickInternal(Unknown Source:0) at android.view.View$PerformClick.run(View.java:31785) at android.os.Handler.handleCallback(Handler.java:1041) at android.os.Handler.dispatchMessage(Handler.java:103) at android.os.Looper.dispatchMessage(Looper.java:315) at android.os.Looper.loopOnce(Looper.java:251) at android.os.Looper.loop(Looper.java:349) at android.app.ActivityThread.main(ActivityThread.java:9041) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)

When reporting a ticket and having a printscreen automatically taken after shaking the device, the screenshot taken becomes blank after typing something in the email or any other field. It happens a bit randomly, but in most of cases.

SHKShakeConfiguration.h is missing nullability annotations, and warns: pointer is missing a nullability type specifier (_nonnull _nullable or _null_unspecified) In our case, we actually have to disable this warning entirely in our primary app target to integrate Shake, which is really bad IMO. I believe this is because Shake is distributed as an XCFramework, incidentally. But either way, the lack of nullability annotations is clearly an oversight since you do it everywhere else throughout the framework as far as I can tell.

Invalid Executable. The executable '/Frameworks/Shake.framework/Shake' contains bitcode. On XCode 16

When running the Leaks tool in Xcode Instruments, Shake shows a memory leak related to "setEnabled". I don't have any access to the source code, but I have tried to remove and update my configurations to see if this has any effect on the leak, but it does not. Attached is a screenshot of a typical profiling session containing the leak, which is triggered immediately after invoking shake at AppDelegate's didFinishLaunchingWithOptions. Using Shake SDK 17.0.2 I can provide a full trace debug file if needed - just email me! :)

When I, as an admin, close or delete an issue, I want the chat thread to also disappear from the user view. Otherwise, I have closed it and cannot see it, but the user can still see the chat issue.

Hello, I'm facing this issue on our Crashlytics dashboard and here is the full stacktrace with additional details. I suspect it's some edge-case caused by the pre-launch report on GooglePlay dashboard, because I couldn't reproduce it, but I would like to hear your thoughts. Thank you, Emanuele Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.myapp/com.shakebugs.shake.ui.ShakeActivity}: android.view.InflateException: Binary XML file line #14: Binary XML file line #13: Error inflating class com.shakebugs.shake.internal.ui.base.view.ShakeToolbarView at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2778) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2856) at android.app.ActivityThread.-wrap11() at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1589) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:164) at android.app.ActivityThread.main(ActivityThread.java:6494) at java.lang.reflect.Method.invoke(Method.java) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807) Android SDK version: 16.2.5 Device Brand: Google Model: Nexus 5X Orientation: Portrait RAM free: 1.25 GB Disk free: 381.43 MB Operating System Version: Android 8.1.0 Orientation: Portrait Rooted: No

We've noted that Shake appears to be writing a few files with an NSFileProtection of None to the disk. The following files were marked as unprotected: shake.sqlite3 shk_log_2023-10-27.log Ideally, we'd like these files to be protected if they are written to disk.

If user doesn’t have enough storage on device (iOS) Shake causes crash

Hello, getting a crash, stack trace Fatal Exception: java.lang.ArrayIndexOutOfBoundsException: length=0; index=-1 at java.util.ArrayList.get( ArrayList.java:439 ) at com.shakebugs.shake.internal.e2.a(SourceFile:17) at com.shakebugs.shake.internal.e2.b(SourceFile:8) at com.shakebugs.shake.internal.f4.a(SourceFile:38) at com.shakebugs.shake.internal.x2.a(SourceFile:16) at com.shakebugs.shake.internal.x2.a(SourceFile:3) at com.shakebugs.shake.internal.x2$b$a.invokeSuspend(SourceFile:1) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:106) at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:115) at kotlinx.coroutines.scheduling.TaskImpl.run (Tasks.kt:100) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)