Bugs

This issue occurs intermittently on app cold start when the user data request is delayed or the session is near expiry. In those cases, Shake creates a report without attaching the signed-in user, even though registration of user ID is performed. After it happens once, later reports may also lose user details even after logout/login or fresh install. Tried: updateUserID() did not fix it. updateUserMetadata(...) did not fix it. setMetadata("user_id", userId) only adds metadata to the ticket, but helped proving the user ID is correctly sent from our side (see attached screenshots).

We've encountered on both Android and iOS devices some instances where the shaking action doesn't do anything, it doesn't trigger the Shakebugs UI to show up in our app. For example, I can 100% reproduce the following test case in our Android app: open the app, wait for all Shake SDK methods to be called by our app: Shake.getReportConfiguration().apply {...} Shake.start(application, apiKey) Shake.setMetadata(...) Shake.registerUser(...) Shake.updateUserMetadata(..) shake the device nothing happens either put the device in sleep (press Screen lock physical button) OR minimize our app & then bring it back into foreground shake the device again ShakeBugs UI appears The expected outcome would be that step 6 should happen directly instead of step 3.

I have multiple issues with the web version for shake. If many requests are pending shake init takes a long time, it's loading and waiting for requests to finish. Therefore the User Experience is really bad with it if the network is slow. Even though Shake waits for all the requests to finish, it sends only requests that was captured BEFORE the button press, making the wait unnecessary and useless. Shake doesn't log with isNetworkRequestsEnabled = true requests like Keycloak init requests and other

After submitting a bug several screens on my app have their bottom safe area adjusted - it looks like for the space needed for the keyboard - even though it is no longer there. This only happens when Shake is dismissed by tapping the 'submit' button, it doesn't happen if I exit Shake with the close/X button.

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.

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! :)

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