Unity.call function does not survive multiple page loads on iOS and OS X
Nobody has claimed this yet.
- Dominant language
- Objective-C++
- Stars
- 2.7k
- Forks
- 734
- Avg merge
- 11h 39m
- Merged PRs (30d)
- 1
Description
The Unity.call() function that is injected by SampleWebView.cs stops working on iOS and OS X if you change the page. (For instance, load to an initial page, click on a link, then hit the back button.)
This does not appear to be broken on Android, which seems to inject the same functionality through a different path.
This is fixed by manually opening the unity: in your JS, rather than using the Unity.call() function.
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.
Research direction
Start with SampleWebView.cs and trace how Unity.call() is injected on iOS and OS X across page navigation, then compare that path with Android's implementation. Reproduce the issue by loading a page, following a link, and using the back button; done means Unity.call() still works after multiple page loads without manually opening unity: in JavaScript.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, csharp, objective-c, unity
- Domain
- desktop-dev, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100