Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check failed: !g_instance error on access again to page #117

Open
MobileD3v3l opened this issue Apr 19, 2024 · 4 comments
Open

Check failed: !g_instance error on access again to page #117

MobileD3v3l opened this issue Apr 19, 2024 · 4 comments

Comments

@MobileD3v3l
Copy link

Hello,

Following the example proposed in the plugin, if I navigate to that page from a home page it is displayed correctly.

However, when you navigate back to the source page and access in again, the application closes and displays the following message on the terminal:

[0419/092055.443214:FATAL:webview_handler.cc(36)] Verification failed: !g_instance.

What could be the problem?

I have consulted some of the previous issues related to !g_instance, but I have not been able to find the solution.

Greetings

@SinyimZhi
Copy link
Collaborator

SinyimZhi commented Apr 19, 2024

Same question as #96

@SinyimZhi
Copy link
Collaborator

Hi, every one. I've merged multi instance and multi window support branch to main. There is a lot of problems might have been resloved. Could you guys help us to verify what we did success and what new problem brought in? @MobileD3v3l

@MobileD3v3l
Copy link
Author

After some tests it seems working correctly. Only one thing, but I need to investigate it deeper as maybe is something on my implementation, JSchannels seem to be lost the second time the app access the webview.

@SinyimZhi
Copy link
Collaborator

After some tests it seems working correctly. Only one thing, but I need to investigate it deeper as maybe is something on my implementation, JSchannels seem to be lost the second time the app access the webview.

Jschannel needs to be injected every time a page is loaded, and it‘s lifecycle is affected by the lifecycle of the page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants