I’m on Unity 2021.1.0f1 and I can only download version 1.16.16 while there is the 1.17.15 released today (and 1.15.13 already 8 days ago).
Even if I enable the Pre-release option it doesn’t help:
I tried also to uninstall it but it doesn’t work.
I found a thread suggesting to delete the package from the Asset Store-5.x, but the Addressable package is not cached there.
Any tips on how to proceed?
Do you have ‘Preview’ packages enabled in the Package Manager filter dropdown? Unsure if the UI changed in 2020x and newer, but in the older 2019x versions you had to click the dropdown & select ‘Preview’ and/or ‘All’ (instead of ‘Already In Project’ or similar).
There are no other options. In the main Package Manager window there are no other filters except this:
I recommend putting in a bug report on this.
I, too, am stuck on Addressables 1.16.19. Newer versions are not shown. I have pre-release packages enabled, but it shouldn’t even matter as there are more recent stable versions. I’m on Unity 2021.1.12f1.
Now, I tried force-updating to the latest version 1.18.15 by putting that into manifest.json. It seemed to work fine at first, but then the build started behaving weirdly: non-addressable Scripts and Prefabs referenced by addressable Scenes went missing, leading to all sorts of janky behaviour and weird drawing in builds. Editor still works fine.
Is there some breaking change that means you can’t update an existing Addressables setup from 1.16.19 to 1.18.15? Any way to work around this? I’d really like to use the new WaitForCompletion API, but currently can’t.
Im also on 1.16.9 and cannot update to latest. Not sure why but I need to.
Unity version 2020.3.13f1.
I used 1.19.9. after change 1.19.17.
I can’t downgrade another version.Only Back to 1.19.9
Hey all, this kind of sounds like issues with Package Manager to me. You might check out Unity Engine - Unity Discussions and let them know what you’re seeing.
@Daerst that’s bizarre. If it’s an issue on our end, try cleaning your build cache and rebuilding. Otherwise, I suppose it could be some weirdness with package manager not liking that version of the package in that version of the Editor. Though, I will say I’ve never seen anything like that when manually editing my manifest.json.
Package manager behaves different in several versions of the Editor, sometimes in subtle ways. Try over on their forums and see if you can get some answers. Also, feel free to file bugs using the link Trey sent. I’d imagine those bugs get in front of the Package manager team.