Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.1
2022.2
2022.2.0a13
Issue ID
1427237
Regression
No
[WebPlatform][iOS] App crashes with URP project
How to reproduce:
1. Create a new URP Unity Project
2. Select WebGL platform
3. Enable "Development Build" in Build Settings
4. Build the project
5. Navigate to the build folder through the terminal e.g., cd /Users/username/unity_project/Build
6. Start a webserver with: http-server --port 8080
7. The webserver should show the address with the local IP of your Mac on the console, e.g., http://192.168.0.191:8080
8. Open this address on iOS device that is connected to the same network
9. Observe app
Expected result: App is launched
Actual result: App crashes with error "RuntimeError: call_indirect to a null table entry (evaluating 'dynCall_iiii(index,a1,a2,a3)')"
Reproducible: 2022.2.0a13
Reproducible on:
iPhone 13 Pro, A15, 15.4.1 (Chrome, Safari)
Not reproducible:
Samsung Galaxy S21 Ultra (Chrome, Samsung Browser)
VLNQA00287, Motorola moto g(7) power (moto g(7) power), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506 (Chrome)
Google Pixel 6, Android 12, GPU: Mali-G78 (Chrome)
MacBook Pro (16-inch, 2021), 12.0 OS version (Chrome)
Full error:
RuntimeError: call_indirect to a null table entry (evaluating 'dynCall_iiii(index,a1,a2,a3)')
<?>.wasm-function[5098]@[wasm code]
<?>.wasm-function[1567]@[wasm code]
<?>.wasm-function[6590]@[wasm code]
<?>.wasm-function[911]@[wasm code]
<?>.wasm-function[6394]@[wasm code]
<?>.wasm-function[3103]@[wasm code]
<?>.wasm-function[64936]@[wasm code]
<?>.wasm-function[27792]@[wasm code]
<?>.wasm-function[14586]@[wasm code]
<?>.wasm-function[14824]@[wasm code]
<?>.wasm-function[28509]@[wasm code]
<?>.wasm-function[14859]@[wasm code]
<?>.wasm-function[66487]@[wasm code]
<?>.wasm-function[14565]@[wasm code]
<?>.wasm-function[14566]@[wasm code]
<?>.wasm-function[64999]@[wasm code]
<?>.wasm-function[64323]@[wasm code]
<?>.wasm-function[7614]@[wasm code]
<?>.wasm-function[9539]@[wasm code]
<?>.wasm-function[45341]@[wasm code]
wasm-stub@[native code]
invoke_iiii@http://192.168.166.80:8080/Build/TrunkURPBuildWebGL.framework.js:3:368855
<?>.wasm-function[45341]@[wasm code]
<?>.wasm-function[1740]@[wasm code]
<?>.wasm-function[23072]@[wasm code]
<?>.wasm-function[839]@[wasm code]
<?>.wasm-function[8806]@[wasm code]
<?>.wasm-function[839]@[wasm code]
<?>.wasm-function[19508]@[wasm code]
<?>.wasm-function[3306]@[wasm code]
<?>.wasm-function[55406]@[wasm code]
<?>.wasm-function[12042]@[wasm code]
<?>.wasm-function[12043]@[wasm code]
<?>.wasm-function[45353]@[wasm code]
wasm-stub@[native code]
@http://192.168.166.80:8080/Build/TrunkURPBuildWebGL.framework.js:3:303921
callMain@http://192.168.166.80:8080/Build/TrunkURPBuildWebGL.framework.js:3:388323
doRun@http://192.168.166.80:8080/Build/TrunkURPBuildWebGL.framework.js:3:388878
run@http://192.168.166.80:8080/Build/TrunkURPBuildWebGL.framework.js:3:389047
runCaller@http://192.168.166.80:8080/Build/TrunkURPBuildWebGL.framework.js:3:387972
removeRunDependency@http://192.168.166.80:8080/Build/TrunkURPBuildWebGL.framework.js:3:16097
@http://192.168.166.80:8080/Build/TrunkURPBuildWebGL.framework.js:3:1967
doCallback@http://192.168.166.80:8080/
Comments (1)
-
Bhonga
Oct 18, 2023 19:35
что значит проблема третьей стороны как мне это модерации объяснить которая игру не пропускает мою
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
Resolution Note:
This bug was a result of a WebAssembly problem with the Safari browser included with iOS 15.4. This issue has now been fixed in iOS 15.5