Abort() at jsStackTrace... webAR error

Bug Reports
#1

Issue:
I have created a relatively simple scene in Unity which I have built and published to Zapworks. So far, seemingly at random, some devices cannot load the web app on their phone and it instead spits this error out once the progress bar reaches about 90%:

abort() at [jsStackTrace@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:20308](mailto:jsStackTrace@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:20308)

[stackTrace@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:20593](mailto:stackTrace@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:20593)

[abort@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:1002](mailto:abort@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:1002)

[___cxa_allocate_exception@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:47838](mailto:___cxa_allocate_exception@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:47838)

wasm-stub@[wasm code]

<?>.wasm-function[804]@[wasm code]

<?>.wasm-function[27696]@[wasm code]

wasm-stub@[native code]

[invoke_vii@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:371755](mailto:invoke_vii@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:371755)

<?>.wasm-function[27696]@[wasm code]

<?>.wasm-function[764]@[wasm code]

<?>.wasm-function[973]@[wasm code]

<?>.wasm-function[44682]@[wasm code]

<?>.wasm-function[18458]@[wasm code]

<?>.wasm-function[633]@[wasm code]

<?>.wasm-function[21968]@[wasm code]

<?>.wasm-function[1878]@[wasm code]

<?>.wasm-function[19181]@[wasm code]

<?>.wasm-function[19177]@[wasm code]

<?>.wasm-function[19178]@[wasm code]

<?>.wasm-function[39170]@[wasm code]

<?>.wasm-function[7412]@[wasm code]

<?>.wasm-function[27694]@[wasm code]

wasm-stub@[native code]

[invoke_iiii@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:372433](mailto:invoke_iiii@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:372433)

<?>.wasm-function[27694]@[wasm code]

<?>.wasm-function[1380]@[wasm code]

<?>.wasm-function[18195]@[wasm code ]

<?>.wasm-function[6627]@[wasm code]

<?>.wasm-function[805]@[wasm code]

<?>.wasm-function[17992]@[wasm code]

<?>.wasm-function[17990]@[wasm code]

<?>.wasm-function[18011]@[wasm code]

<?>.wasm-function[17935]@[wasm code]

<?>.wasm-function[37500]@[wasm code]

<?>.wasm-function[18051]@[wasm code]

<?>.wasm-function[6656]@[wasm code]

<?>.wasm-function[6655]@[wasm code]

<?>.wasm-function[31746]@[wasm code]

<?>.wasm-function[15249]@[wasm code]

<?>.wasm-function[15248]@[wasm code]

<?>.wasm-function[6670]@[wasm code]

<?>.wasm-function[27707]@[wasm code]

wasm-stub@[native code]

@blob:https://302y2.zappar.io/3627936f-4de6-4bb2-bc4d-6d9824c4ae69:3:316524

[callMain@blob:https://302y2.zappar.io/3627936f-4de6-4b](mailto:callMain@blob:https://302y2.zappar.io/3627936f-4de6-4b)

Affecting:

The devices I have tested this on are:
1 x iPhone 12 (erroneous)
3 x iPhone 13 (2 work 1 erroneous)
1 x iPhone 13Pro (erroneous)
2 x Samsung S21 (1 erroneous 1 works)
1 x Samsung S22 Ultra (works)

Workaround:

I initially got this error on one of the iPhone 13s but it eventually worked after I tried loading the app again the next day. No idea why!

Any help and tips would be appreciated. I don’t know much about coding other than programming logic, so this error code is rather alien to me.

1 Like
#2

Hi @jordan.may,

I wonder if you could ensure that your project is optimised for hosting by going to the Zappar menu in Unity, heading to Editor and then selecting Update Project Settings To Publish before building your experience?

Additionally, please may you ensure that you are using the correct Zappar WebGL template for your version of Unity?

You could also try the tips from this thread:

Have a great day,
Francesca :blush:

#3

Hi Francesca,

Thank you for your reply!
I managed to diagnose the issue, and it turns out all the erroneous devices were ones that were not up to date with their operating system. So after the iPhones updated, it worked! I wasn’t aware that the phone’s OS version mattered, so that’s good to know.

And yes, the correct template was used, although I have not selected ‘Update Project Settings To Publish’ but set the publish settings myself, which seems to have worked.

Thanks for the thread link too!

1 Like
#4

Hi @jordan.may,

That’s great, thanks for updating the thread!

You make some great points which are super helpful for the community. :rocket: :zap:

Have an awesome day,
Francesca :blush: