Asset not reachable in same local group after content update

Unity Engine
1

hi, I’m new in addressable,
recently I occur a problem

since I have a local build/load group setting with static content (can’t change post release)
it have “AssetA”, “AssetB”, “AssetC”
now I can use them on Android device as built-in assets with “v1.apk”.

and then follow content update steps to update “AssetA”,
“AssetA” now is in content update group and mark as remote build/load group (can change post release)

then my Android device’s app with “v1.apk” after update catalog,
generally I can use “AssetA”, "AssetB, “AssetC”, right?
but the situation I encounter is that I can only use new version of “AssetA”,
local version of “AssetB”, “AssetC” is not reachable to use.

is it a normal situation? or I use content update with a wrong way?

2

this sounds similar to https://discussions.unity.com/t/749057

3

thanks, it’s just the problem I encounter.
it can be reproduce @ Unity 2019.2.0f1 and 2019.3.0f3 both with Addressables 1.5.0
simply use partial of non-hash naming or no crc still has same problem
now I use non-hash naming + no crc at same time to avoid that