Frequently asked questions
1. What is the memory footprint of Bugsee iOS SDK?
Precise amount of RAM used by Bugsee depends on the device specifications and application behavior (e.g. screen resolution, frame rate, etc). The generic application case is presented in the table below.
| Bugsee state | Bugsee RAM footprint (MB) |
|---|---|
| Not launched | 44 |
| Enabled | 60 |
These values were produced by testing Bugsee SDK in a sample application on iPhone Xs.
2. It takes too much time for the report to appear in the Bugsee web dashboard. Why?
Please check the following:
- Make sure Internet is available on the device (e.g. try to open a web page in the browser)
- Make sure you don't have WifiOnlyUpload enabled via launch options. If it's enabled, you need to be connected to WiFi for the report to be uploaded.
- If you're trying to upload crash report, you need to relaunch the application to trigger the upload. Crash report is uploaded on the next application launch.
3. Crash report does not appear in Bugsee dashboard. Why?
- Make sure Internet is available on the device (e.g. try to open a web page in the browser)
- Make sure you don't have WifiOnlyUpload enabled via launch options. If it's enabled, you need to be connected to WiFi for the report to be uploaded.
- Make sure you're not triggering the crash with Debugger attached. When Debugger is attached, it will handle the signal/unhandled exception and will not let Bugsee to handle it.
- If you're using multiple crash reporting tools, try disabling other crash reporters. It's a known limitation that crash reporters may interfere with each other.
- If you're trying to upload crash report, you need to relaunch the application to trigger the upload. Crash report is uploaded on the next application launch.
If your question is not listed here, please let us know at support@bugsee.com