Test if running on simulator

Is there any way from monkeyc to test if the program is running on the simulator or on real hardware so I can initialize some data differently?

Thanks,

Dave.

Top Replies

travis.vitek over 8 years ago +1

It appears that the 2.2.0 SDK now gives non-zero values for the firmwareVersion, so the above code no longer works. While it isn't as nice as a runtime check, it seems that you should be able to do conditionally…
beva 15 days ago +1

I wonder if System.getDeviceSettings().uniqueIdentifier is constant and unique for each installed simulator. Or is there already another solution except conditional compiling?

All Replies

flocsy🤠 14 days ago in reply to Ultra

no, :test is only kept when running tests

Ultra 14 days ago in reply to flocsy🤠

Okay but you could still use :debug and :release if you only deploy the release version to devices.

flocsy🤠 14 days ago in reply to Ultra

And that's what most of us use, but it's not 100%

It's good for not releasing accidentally some thing not meant for release.

But sometimes you do want (or need to) run release build in the simulator. Although in most of those cases you probably would want to run release (non-emulator) code anyways (i.e DataField on old device with not enough memory or trying to recreate a crash from ERA)

Ultra 13 days ago in reply to flocsy🤠

Then you could set a storage value in debug mode. Which in theory only gets set in Simulator. Then if you subsequently run release in Simulator it can work in same manner. Like you say depends on needs. You just need a system works for 99% of time, and can be quickly tweaked for those 1% or less of cases.

beva 13 days ago

For now this is good enough and 'simulator' code will never endup with end users. This way I can overrule the onpress functionallity with an extra setting to cycle through test situations.