This change is usually fine (although the current implementation seems to be creating more clashes than it is supposed to solve, so that's an issue as well), but also affects the location of /Data/{bundleID} which I want to direct the player towards for importing/exporting user content. It's not technically impossible now, but instructing "navigate to /Data/user.*********.game" feels rather iffy.
Sideloading currently updates the bundleID in a way that makes clashes/overwrites more likely.
This behaviour (and specifically the effect on the data location, not sure if the bundleId is relevant for devs otherwise) is not documented.
Is there a way to prevent this from happening so that players can be instructed a bit more accurately (for the usecase of e.g. importing/exporting level data)?
This covers both the user.1234.audition and com.gingerbeardman.audition folder names if you've structured your bundleID in the recommended reverse DNS notation.
Unless I'm misunderstand things, the only possibility of a clash would be if one user installs two apps with the same final part of the bundleID.
Have you seen such as clash with apps that have the correct reverse DNS bundleID? Real examples would be helpful to get this looked at.
If you sideload multiple versions of the same game, only the latest version will be available on your device. However, if you sideloaded through the Playdate website before February 2023, later versions of the game will appear as a new game. This is due to a change we made to how the games’ unique identifiers are handled, which will improve sideloading.
I noticed this change indeed, seems like the full bundleID is now included which would reduce the chance of a clash significantly.
Still, the “user.12345” prefix is added which does not add any entropy (since it’s static for each user) and looks a bit messy IMHO. Again, for most games this does not matter, but when directing the user to the Data folder it makes things unnecessarily, even if only slightly, more diffficult.
Would be great to hear the reasoning behind this, because as far as I can see, the intended effect is impossible to achieve without requiring devs to register and “sign” a bundleID through some centralised way (or, alternatively, treat every update as a new game, which is obviously not great).