Are you sure that test is enough on android ? I have something like more complex https://github.com/nativescript-community/extendedinfo/blob/master/src/extendedinfo.android.ts#L4
Also you should cache the value
It is a simple Boolean when cached while the test requires a lot more operations

And to.me that name is far too long :) we don't really care about the fact that iios and android don't use the se name convention

Hi, I think that @farfromrefug is a better solution, in fact I've adopted solution from flutter:

https://github.com/flutter/plugins/blob/master/packages/device_info/device_info/android/src/main/java/io/flutter/plugins/deviceinfo/MethodCallHandlerImpl.java

@mapo80 your link was wrong here is the good link https://github.com/flutter/plugins/blob/master/packages/device_info/device_info/android/src/main/java/io/flutter/plugins/deviceinfo/MethodCallHandlerImpl.java

@mapo80 your link was wrong here is the good link https://github.com/flutter/plugins/blob/master/packages/device_info/device_info/android/src/main/java/io/flutter/plugins/deviceinfo/MethodCallHandlerImpl.java

Fixed, thanks!

Instead we should add the additional checks that are used by other frameworks/plugins to beef up the detection of a simulator vs real device so the original export function isRealDevice(): boolean; function is correct on both platforms again.

@NathanaelA The reason behind the new function implementation is that it does not present a breaking change. If isRealDevice is fixed then it can lead to breaking changes, since other framework functions (and potentially many client apps) use the result of this call incorrectly. In other words, on iOS when the device is real, it returns paths, which are being used elsewhere - removing this would result in a breaking change.

Are you sure that test is enough on android ? I have something like more complex https://github.com/nativescript-community/extendedinfo/blob/master/src/extendedinfo.android.ts#L4
Also you should cache the value
It is a simple Boolean when cached while the test requires a lot more operations

And to.me that name is far too long :) we don't really care about the fact that iios and android don't use the se name convention

@farfromrefug perhaps there may be a style guide that states how long function names can be and how specific they need to be, but for now, I don't think there is one. Renaming this is fine as long as it is clear what the function does. Calling the function isEmulator hints at being specific to Android. Calling it isSimulator hints at being specific to iOS. This function name is clear and it relates that it is a cross platform function.

@NathanaelA totally agree with you that isRealDevice should be fixed, but disagree with you that it is not a breaking change. This is a public API and plugins as well as other client apps could be using isRealDevice as it is. If the fix is implemented, then it will break those. This PR is added functionality that will allow isRealDevice usage to continue as is, without breaking anything, but also provide a good step forward for fixing it in the future, as well as providing the needed simulator check right now.

@NathanaelA fair point. However, isRealDevice also returns the opposite of the truth on Android. So therefore it return true when run on an Emulator. This would be a breaking change.

I for one did not even know it was there! I doubt many apps/ plugins use it today

testing