both async and sync fetching of the wasm failed

Open
#160 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ios, react, typescript, wasm
Domain
frontend, mobile-dev

Research direction

The report names no source file, test, or entry point. Start by reproducing the wasm fetch failure on an iPhone 6s Plus running iOS 13.6.1, then trace the runtime's async and sync wasm loading paths with assertions enabled. Done means the Rive React runtime loads wasm successfully on that device while preserving behavior on iPhone 12.

Written by the indexing model from the issue text.

Description

needs-repro

Aborted(both async and sync fetching of the wasm failed). Build with -sASSERTIONS for more info. (evaluating 'new WebAssembly.RuntimeError(t+". Build with -sASSERTIONS for more info.")')

device: iphone 6s Plus
System: ios 13.6.1

but work fine on iphone12

Dominant language
TypeScript
Stars
1.2k
Forks
58
Avg merge
3h 23m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rive-app/rive-react

All issues in rive-app/rive-react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.