Ticket Created
over 5 years ago

WERETECH-8439

Vivoactive 3 doesn't support BLE, but manifest file allows the combination to be selected

Vivoactive 3 doesn't support BLE, but manifest file allows the combination to be selected. If you then try and run this on the simulator or a real device it will crash as soon as any call to BLE is made.

markdotai
Parents
  • over 5 years ago in reply to jim_m_58

    Yep I realise now how the current flag works Slight smile That's why I was suggesting a new flag instead of modifying the current one.

    But how does App Migration in the store settings work when it says: "Allow the app store to add support for newly compatible devices?" When it can't know what devices are compatible with an app? Maybe a new device (e.g. 255) gets released in the future which doesn't support BLE, and a 655 gets released which does support BLE (and a 655 music which doesn't!). How would the app store know that my particular app will crash if BLE isn't supported and which devices to allow migration to. Or does App Migration never actually occur in reality?

Comment
  • over 5 years ago in reply to jim_m_58

    Yep I realise now how the current flag works Slight smile That's why I was suggesting a new flag instead of modifying the current one.

    But how does App Migration in the store settings work when it says: "Allow the app store to add support for newly compatible devices?" When it can't know what devices are compatible with an app? Maybe a new device (e.g. 255) gets released in the future which doesn't support BLE, and a 655 gets released which does support BLE (and a 655 music which doesn't!). How would the app store know that my particular app will crash if BLE isn't supported and which devices to allow migration to. Or does App Migration never actually occur in reality?

Children
  • over 5 years ago in reply to markdotai

    One thing to understand is that app migration can have issues based on the app itself and that's why there's an option to disable it on an app by app basis (I have it off on a number of things.)

    The 23x/735 was interesting because the 23x was ciq1 and the 735, ciq2.  They had the same basics (screen shape and size, etc), but if a 735 variant was added, things could be auto migrated to it from the 23x which was a problem.  The va3 and s60 was another case where overall, CIQ was the same, but the S60 doesn't have a baro, and things could get auto-migrated to the S60 that depended on a baro.

    There's no need for an extra flag (you'd need to add a whole bunch for similar situations with other things.).  All it takes is ensuring that a target works correctly in the sim when you add it to the manifest, and will can depend very much on the app itself and how it was written..  Tricks you learn over time.