#3657
  • Created on
    2023-12-08 00:30
  • Reported by
    egouge
  • Status
    Test
  • Priority
    Normal (3)
  • Assigned to
    darrinc
  • Milestone
    8.0.0
  • Plan Level
    -
  • Estimate
    0.0
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

SMARTMobile - Add smart_mobile_min_build to Project.json 

"smart_version" gives Mobile a way to decide what it supports, but we want the other way around as well.

Here is the full scenario:
1. Add "smart_mobile_min_build" to the project.json and set it to 1 (integer)
2. Mobile reads that field and if it is greater than its build number we fail with a simple message that says you need to upgrade
3. Now SMART 9 comes out and we want everyone on at least mobile build 480. You change "smart_mobile_min_build" to 480 in the package.
4. Users trying to load SMART 9 packages see the message and then upgrade Mobile

This gets us out of the problem of having to make the package format always do sane things on very old builds.
User picture
  on 2023-12-08 21:27 *
By egouge 
 Default is 0, which means no restriction. Please set it to 1 (integer) when you add it. Desktop can ship with it being whatever the latest app store version is. I will confirm this strategy with Jonathan as we might only invoke it when the package format starts to diverge.
User picture
  on 2024-02-08 23:36 *
By egouge
Assigned to set to egouge

In smart-cs:9229 re: #3657

Committed to: smart-cs

User picture
  on 2024-02-08 23:36 *
By egouge
Status changed from New to Test
User picture
  on 2024-02-10 00:53 *
By egouge
Tags added 8.0 - SMART Mobile Feature
User picture
  on 2024-02-10 00:53 *
By egouge
Assigned to changed from egouge to darrinc
ready for testing in 2024-02-09 build
User picture
  on 2024-02-12 22:00 *
By darrinc
In the 2024-02-09 build, the project.json file now includes the smart_mobile_min_build option but it has not been tested in Mobile and once an updated version of Mobile is available testing will take place on the mobile software as well.