feat(device_info_plus)!: Return model name for iOS and MacOS devices

[vbuberen]

Description

Long awaited feature to show device names that are known to users. Marking as breaking, because I changed the API.

On iOS model field now returns names like iPhone 15 Pro, etc. instead of just iPhone, iPad.

Screenshot from iPhone with model name

On MacOS the plugin returns modelName and modelIdentifier fields instead of just model which was returning identifier earlier.

Screenshot from MacBook with model name and identifier

Related Issues

Closes #2656

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
• No, this is not a breaking change.

[vbuberen]

For these lists I wasn't sure if we need to specify CPU model, like it is done on Apple's website but decided that it is redundant info.

[vbuberen]

Don't know why iOS integration test fails.

[miquelbeltran]

LGTM!

[miquelbeltran]

Don't know why iOS integration test fails.

Could be that increasing the minimum deployment target makes these properties mandatory:

Warning: Missing build name (CFBundleShortVersionString).
Warning: Missing build number (CFBundleVersion).
ERROR: Action Required: You must set a build name and number in the pubspec.yaml file version field before submitting to the App Store.

You can try to add a version here: https://github.com/fluttercommunity/plus_plugins/blob/main/packages/device_info_plus/device_info_plus/example/pubspec.yaml

[vbuberen]

Could be that increasing the minimum deployment target makes these properties mandatory:

I saw these warnings earlier, but still tried to add version - still failing. Will investigate later.

[StanleyCocos]

This feature is needed by many people, but the downside is that maintenance can be troublesome. After Apple releases new devices, we need to update the code promptly.

Therefore, I suggest changing the "Unknown Model" returned in modelName to modelIdentifier. This would avoid situations where modelName == Unknown Model, and we might need to use modelIdentifier in conjunction with it to determine the device information accurately.

[vbuberen]

This feature is needed by many people, but the downside is that maintenance can be troublesome. After Apple releases new devices, we need to update the code promptly.

This is not an issue with current pace of product releases from Apple. It is not a big deal to report the missing model. Returning modelIdentifier won't solve anything and it is better to show that the model is unknown explicitly than to create a confusion with returning modelIdentifier 2 times. So don't agree with this suggestion.