Apps not auto-migrating to Venu 3?

I think in this case it's because the screen resolution is different for Venu 3/3S vs. Venu 2/2S. There are seemingly other reasons to block auto-migration, but this is the most common one I've noticed. If an existing device does not have a next-gen variant with the same resolution, then it's pretty much a given it won't be auto-migrated.

Venu 2: 416x416
Venus 2S: 360x360

Venu 3: 454x454
Venu 3S: 390x390

Ah, that makes sense, thx

One thing to note with the venu3/3s is that it's got "wheelchair mode" which impacts any app that uses steps/stepGoal.

You can test this in the sim with "settings>wheelchair mode".  When this is checked, under "simulation>Activity Monitoring>Set Activity Monitor Info" you see pushes instead of steps and pushGoal instead of stepGoal.  At a minimum you want to check for a crash in wheelchair mode, but you probably want to use pushes instead of steps in wheelchair mode

yes

And this can be a bit tricky.  I wish there was something like System.getDeviceSettings().isWheelchair, but there's not.  Per Brandon, right now check for pushes!=0, but I've also found that in the sim, the stepGoal will be 0 if in wheelchair mode. Not sure if that's the case on a real device though....

Now I wonder about the move bar.  Is that even a thing in wheelchair mode?  I see it in the sim, but what about the actual venu3/3s in wheelchair mode?

Brandon.ConnectIQ advise  doesn't work on sim as I've mentioned in

https://forums.garmin.com/developer/connect-iq/i/bug-reports/no-iswheelchairmode-flag

According to the doc, now, most members can be null e.g. steps, movebar level, ..., so I don't know if it's truth or only trick to not specify members with values.

Simulation of activity also doesn't run for wheelchair so I don't know if movebar is connected with pushes.

Soon ERA will give us an answer :-)