versa lite crash but not simulator

[CharliesGal]

I made a clockface which works fine on my Ionic. 

I have tried to modify it to work on Versa and Versa Lite. 

It works on the Simulator for Versa and Lite with no problems. 

When I submitted it for review, it was rejected because they say it crashes on the Versa Lite. 

Since I own an Ionic and not Versa Lite I am not able to test this on a device. 

Any suggestions on how I solve this problem, since i am not able to recreate the issue?

https://gallery.fitbit.com/details/29a7281f-5247-4c90-975d-0343c69ad815

or 

https://gallery.fitbit.com/details/f791b2b1-fce9-4335-85f8-a1d678eab73e 

Build Output says : 

• Building app for Fitbit Ionic
• Building app for Fitbit Versa
• Building app for Fitbit Versa Lite
• Building companion
• Building settings
• App UUID: 29a7281f-5247-4c90-975d-0343c69ad815, BuildID: 0x0b58558f14c277b7

Console says: 

[10:28:52 AM]Sideload successful!

[HOST][10:28:52 AM]App Closed

[HOST][10:28:53 AM]App Started

It runs just fine on the Simulator. 

[Durus]

Did you get a crash report with any details?

[CharliesGal]

No, they didn't give me any other information. 

[Durus]

I would try starting the app in the Versa lite simulator and letting it run for s few hours maybe overnight and see if it crashes.

The Versa only has 64k ram so it's pretty easy to get out of memory errors.

There is a good post about memory usage on the Fitbit.  I'll find it and post it.

[Durus]

Here's the link.

https://github.com/gaperton/ionic-views/blob/master/docs/optimization-guidelines.md#do-not-use-funct...

If you post your code to github or your post your tick event here I could take a look at it.

This might help.  I have a watchface that is in the app gallery.  It's not very complicated but is approved for all 3 devices https://github.com/grumpy-coders/rpg-time

[CharliesGal]

I am not sure if this will solve it or not, but in this post , MolliorMerx mentioned that he needed to code for "Versa L" and not "Versa Lite". If this is correct, it would explain why the clock works on the simulator but not on an actual device. 

I have re-submitted this for review and we shall see....

[ladykayaker]

mistakenly posted here. 

[CharliesGal · Accepted solution]

---

@CharliesGal wrote:

I am not sure if this will solve it or not, but in this post , MolliorMerx mentioned that he needed to code for "Versa L" and not "Versa Lite". If this is correct, it would explain why the clock works on the simulator but not on an actual device. 

I have re-submitted this for review and we shall see....

---

This fixed the problem. 

In the simulator, code for "Versa Lite" but for the device code for "Versa L"

Credit goes to @MolliorMerx who described the solution in this post

[MolliorMerx]

To be fair, it was someone on the dev team at Fitbit that told me the difference between "Versa Lite" and "Versa L"

There are better ways to check for watch type. I'm still learning how to do that myself, but I CAN say don't assume it will stay "Versa L" forever.