When I use connectivity.startMonitoring on Android it implicitly triggers the callback with the current state of the connectivity when I call startMonitoring.
On iOS, it will trigger the callback only when the connectivity changes.
I like the Android behaviour, but that being said iOS sounds more like how it should work.
Anyhow, shouldn't the behaviour be the same in between the two platforms ?
PS: both scenarios are tested on real devices, not simulators.
$ tns info
All NativeScript components versions information
┌──────────────────┬─────────────────┬────────────────┬─────────────┐
│ Component │ Current version │ Latest version │ Information │
│ nativescript │ 3.1.2 │ 3.1.2 │ Up to date │
│ tns-core-modules │ 3.1.0 │ 3.1.0 │ Up to date │
│ tns-android │ 3.1.1 │ 3.1.1 │ Up to date │
│ tns-ios │ 3.1.0 │ 3.1.0 │ Up to date │
└──────────────────┴─────────────────┴────────────────┴─────────────┘
Reactions are currently unavailable
When I use connectivity.startMonitoring on Android it implicitly triggers the callback with the current state of the connectivity when I call startMonitoring.
On iOS, it will trigger the callback only when the connectivity changes.
I like the Android behaviour, but that being said iOS sounds more like how it should work.
Anyhow, shouldn't the behaviour be the same in between the two platforms ?
PS: both scenarios are tested on real devices, not simulators.