I run the Qobuz native app on an ARM-based MacBook Air, and while Autoplay when enabled does show the next track queued and actually plays it on the WiiM Ultra, it is fraught with dropouts that were not occurring during playback of the original album that had just completed. If I try to start and stop that Autoplayed track, or advance to the next one in the queue, that doesn't change anything, playback is still fraught with dropouts.
Additionally, if I change the Connect endpoint to a non-WiiM device in the form of a Raspberry Pi 5 running Volumio Premium, exactly one additional track will Autoplay (without any dropouts) but thats all, even though you can see the next Autoplay track thats been queued, at the end of the currently playing track the playback just stops and the queue returns to the first track of the original album that was playing prior to Autoplay commencing.
So there are definite Autoplay issues with Qobuz Connect right now, and it isn't isolated to WiiM devices nor iOS or Android, the macOS desktop app is also misbehaving too.
Interestingly, if I then grab control of that queue using the Android app, the one track and done Autoplay aspect on the RPi5/Volumio instance does not persist, Autoplay continues normally there, however directing that queue back to the WiiM Ultra doesn't cure the audio dropout problem, and it then inherits the one track and done phenomenon.