SDK 2.2.1 Simulator crashes when trying to view memory

I just installed the new SDK 2.2.1 but now when I try to view the app memory (File -> View Memory) the simulator crashes.

I've tried restarting Eclipse, ensuring any existing simulator processes are killed, rebuilding the project from scratch, etc... anyone have any other ideas? And is anyone else running into this? The View Memory functionality was working fine an hour ago with SDK 2.1.5 before I upgraded.

Cheers,
Douglas

jim_m_58 over 8 years ago

Works fine for me. I'm on Windows 10. Are you on a Mac? (ok .. I see you have a mac from your sig...)

Is it for all projects or just one? (I've tried a few)

Coleman.Apps over 8 years ago

I'm checking this out right now on my mac and will be filing a ticket with my finding and your.

Thanks,

-Coleman

UPDATE: We tested this on OS X 10.9.5 and 10.12 and haven't been able to reproduce. Is this happening with sample apps or with your app specifically?

dbrobert over 8 years ago

I'm checking this out right now on my mac and will be filing a ticket with my finding and your.

Thanks,

-Coleman

UPDATE: We tested this on OS X 10.9.5 and 10.12 and haven't been able to reproduce. Is this happening with sample apps or with your app specifically?

This is on my METAR/TAF widget/app. I tried a couple of other apps and it works fine so it seems to be limited, for me at least, to this one app (so far).

I switched back to 2.1.5 and the view memory functionality worked fine. Then back to SDK 2.2.1 and it crashes when trying to view memory. I've emailed the crash report to the ConnectIQ email address.

Are there any other things I should try? Is there temp folders or caches that perhaps require removal?

Cheers,
Douglas

jim_m_58 over 8 years ago

Are there any other things I should try? Is there temp folders or caches that perhaps require removal?

Cheers,
Douglas

Over time, I have seen a couple of weird simulator things that were resolved by deleting the temp directory used by the sim (sometimes when switching SDKs). I'm not quite sure where it is on a mac, but I'm sure there are posts about it somewhere in the forum. You see the same structure in the temp directory as you see on a watch, if that helps - can you search for something like "apps" on your drive?

dbrobert over 8 years ago

Over time, I have seen a couple of weird simulator things that were resolved by deleting the temp directory used by the sim (sometimes when switching SDKs).

I tried removing the temp directory as part of my initial investigation; it's at $TMPDIR/GARMIN on a Mac.

I have started on working to narrow down the point at which the simulator crashes. When my app initializes it waits for a BLE connection and a GPS position. If I don't simulate data (thus denying the app a GPS position), I'm able to view the memory. But once I get past that and into the main functionality of the widget, trying to view the memory causes the simulator to crash.

Cheers,
Douglas

UPDATE: I installed SDK 2.2.0 (BETA) and the simulator does the same thing. The SDK 2.1.5 simulator view memory functionality works fine, with or without clearing out the TMPDIR.

Coleman.Apps over 8 years ago

I've tried a few things here and I'm still struggling to reproduce your issue. Is your app dependent upon the data it gets via BLE? Are you using ADB to simulate this?

Former Member over 8 years ago

My simulator crashes every time I launch an app.
(eclipse neon and SDK 2.2.1

dbrobert over 8 years ago

I've tried a few things here and I'm still struggling to reproduce your issue. Is you app dependent upon the data it gets via BLE? Are you using ADB to simulate this?

When I say via BLE I mean using standard Communications API requests through GCM; specifically makeJsonRequest(). There is no companion app or anything overly complex per se.

Cheers,
Douglas

Coleman.Apps over 8 years ago

My simulator crashes every time I launch an app.
(eclipse neon and SDK 2.2.1

I believe you are experiencing the issue noted here: https://forums.garmin.com/showthread.php?364576-2-2-1-OSX-Simulator-crashes-on-launch

This is a known issue and there is a workaround listed in the thread. Downloading the SDK through the SDK Manager is likely to fix the issue, but you may need to delete the SDK directory first.

-Coleman

Coleman.Apps over 8 years ago

When I say via BLE I mean using standard Communications API requests through GCM; specifically makeJsonRequest(). There is no companion app or anything overly complex per se.

Cheers,
Douglas

Thanks for the clarification. If it wouldn't be too much to ask to take a look at your source or if you could put together a super paired down version of it for us to try in the sim that would be great. You can email us directly at [email][email protected][/email].

Thanks,
-Coleman