You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on an app that uses this project as well as the Android counterpart, and I noticed that, when using the default settings, the order of states during firmware upgrade is different from one platform to the other.
It seems like the iOS default mode is not TEST_AND_CONFIRM as indicated (and recommended) in the README, but actually CONFIRM_ONLY.
I confirmed this emprically—if I set the Android mode to CONFIRM_ONLY, then Android behaves like the iOS default mode. If I set the iOS mode to TEST_AND_CONFIRM, then iOS behaves like the Android default mode.
I'm working on an app that uses this project as well as the Android counterpart, and I noticed that, when using the default settings, the order of states during firmware upgrade is different from one platform to the other.
It seems like the iOS default mode is not
TEST_AND_CONFIRM
as indicated (and recommended) in the README, but actuallyCONFIRM_ONLY
.I confirmed this emprically—if I set the Android mode to
CONFIRM_ONLY
, then Android behaves like the iOS default mode. If I set the iOS mode toTEST_AND_CONFIRM
, then iOS behaves like the Android default mode.Looks like the default mode is set here
The text was updated successfully, but these errors were encountered: