Addressables are not working on WebGL on new Unity versions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by opening the Scene Loading and Sprite Land examples and reproducing the WebGL build on Unity 2022.1.23f1, 2022.2.0b15, or 2023.1.0a19, then compare it with 2020.3.33f. Investigate the generated Addressables bundle request associated with the reported RemoteProviderException. Done means the examples load their bundles on the newer Unity versions without the no-data error.
Written by the indexing model from the issue text.
Description
Hi,
as said in the title, addressables are not working on WebGL. Tested on 2 examples from this repository: Scene Loading and Sprite Land. They work on their original version (2019.4.9f1) and on 2020.3.33f. When I bump the version to 2022.1.23f1 I'm getting the errors listed below:
Asset Bundle download is complete, but no data have been received
RemoteProviderException : Unable to load asset bundle from : [http://localhost:8000/StreamingAsse...s_all_f4ba373f651003dcc29897ae4302b413.bundle](http://localhost:8000/StreamingAssets/aa/WebGL/defaultlocalgroup_assets_all_f4ba373f651003dcc29897ae4302b413.bundle)
UnityWebRequest result : ConnectionError : Received no data in response
ResponseCode : 200, Method : GET
url : [http://localhost:8000/StreamingAsse...s_all_f4ba373f651003dcc29897ae4302b413.bundle](http://localhost:8000/StreamingAssets/aa/WebGL/defaultlocalgroup_assets_all_f4ba373f651003dcc29897ae4302b413.bundle)
I've checked on versions:
- 2022.1.23f1
- 2022.2.0b15
- 2023.1.0a19
Reproduction steps:
- Get example code from this repository
- Open Scene Loading or Sprite Land
- Bump the unity version to one of the listed above
- Fix any errors that occurred because of version change
- See the errors
- Lower the version to 2020.3.33f
- See no errors
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 303
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Unity-Technologies/Addressables-Sample
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Unity-Technologies/Addressables-Sample#98 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Unity-Technologies/Addressables-Sample#94 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
Unity-Technologies/Addressables-Sample#90 · 1 comment ·
All issues in Unity-Technologies/Addressables-Sample
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#1379 ·
-
priority-0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
StackExchange/StackExchange.Redis#3249 ·
-
[Feat] 조합 영역 구분선 개선 Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100