Small fix for iOS version detection

[HeLau1337]

This PR refers to this comment on issue #26.

The answer to
// TODO: check what systemVersion returns on an actual iOS device. (comment in lib/bloc.dart)
is that ios.systemVersion actually returns the string representation of a double instead of an int. So the fix for this was quite simple.

Debugging output before I made the changes:

There are also many auto-generated changes made by XCode during the iOS build. Most of them look like dependency-updates. But for some reason, it also automatically changed the "PRODUCT_BUNDLE_IDENTIFIER" from
"com.jeroen1602.lighthousePm"
to
"com.jeroen1602.VrLighthousePm".

I have no idea why. @jeroen1602 is this new bundle identifier correct or do you have an idea why this happened?

[HeLau1337]

Oh, I forgot to update the changelog... again ':D
I'm not 100% sure how your versioning works or how you structure and update your changelog, @jeroen1602 .
Do I have to create a "new version section" like "Version 1.1.2 RC" and list my changes/fixes under this new section? Sorry for having to ask this.

[jeroen1602]

I've looked into the bundle id change, and I can't find why it has done it. The good thing is that there hasn't been any iOS release yet, so it isn't a very big problem.

Maybe you have set a setting in xcode somewhere?

[jeroen1602]

This will probably never happen but double.tryParse will return null if it could not parse the number. And null >= 13.0 will throw an exception.

[HeLau1337]

It actually threw these exceptions on iOS when it was int.tryParse instead of double.tryParse. Which also created a never ending Circular Progress Indicator on the settings page where the dropdown menu for the "preferred theme" is.

Should I surround the if-condition with a try-catch where it does simply nothing if it catches an exception (= return false)?

[jeroen1602]

I was thinking about saving the result of double.tryParse() to a variable and extending the if to if (version != null && version >= 13.0)

Maybe crash the app if the version is null and we are running in debug mode.

[jeroen1602]

Oh, I forgot to update the changelog... again ':D
I'm not 100% sure how your versioning works or how you structure and update your changelog, @jeroen1602 .
Do I have to create a "new version section" like "Version 1.1.2 RC" and list my changes/fixes under this new section? Sorry for having to ask this.

Yeah just use Version 1.1.2+7 RC

The RC means release candidate, as in it hasn't been released yet (we're still working on it)
And the 1.1.2 is just normal major.minor.patch, the +7 should always increment (this is what the system uses to compare if there is a new version).

[HeLau1337]

Thanks for the feedback. I'm going to update the PR later today.