Bugs

I'd like to report a crash. According to the logs, the Resume app crashes when Shake hasn't successfully unregistered the ScreenCaptureCallback. Over 4K users have experienced this crash on the same day from our end. Could you please help to resolve this issue?

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)

Binary XML file line #56 in shake_sdk_bottom_sheet_dialog_message: Binary XML file line #56 in shake_sdk_bottom_sheet_dialog_message: Error inflating class com.shakebugs.shake.internal.view.LogoView

Shake only captures the topmost window in our multi-window app, ignoring underlying ones.

We'd lie to report a crash due to Shakebugs sql executing. It seems to be a SQL execution conflicts when other plugins are trying to write data.

Steps to repro send a message from the app Start responding in the dashboard but don't hit send Send another message from the app Send the message on the dashboard Expected Behavior: The message from the dashboard should show up after the last user message in the list. Actual Behavior: The message shows up between the two user messages.