[Bug]: All plugins are "not implemented on android" after upgrading to Capacitor 6

[Linksku]

[Bug]: All plugins are "not implemented on android" after upgrading to Capacitor 6

[ionitron-bot]

This issue needs more information before it can be addressed. In particular, the reporter needs to provide a minimal sample app that demonstrates the issue. If no sample app is provided within 15 days, the issue will be closed.
Please see the Contributing Guide for how to create a Sample App.
Thanks! Ionitron 💙

[Ionitron]

It looks like this issue didn't get the information it needed, so I'll close it for now. If I made a mistake, sorry! I am just a bot.

Have a great day!
Ionitron 💙

[Venryx]

I hit this same issue, where several plugins (including the capacitor-provided "App" plugin) were "not implemented on android". (despite them clearly existing, and my seeing their initializations in the android logs)

Base situation: My app's "public" folder merely held "stub" index.html and index.js files, which would immediately redirect to my web-hosted domain at page load time.

Fix: Rather than use those "stub" files with redirection, instead I just provided my web-hosted domain as the server.url field on capacitor.config.json.

Diagnosis: I think what happened is that somewhere in the updates from Capacitor 4 to 6, the plugin-injection system was optimized to complete earlier in the page loading process. So the redirect that my "stub" index.js file wants to do, used to complete before the page redirect, whereas on Capacitor 6 it completes after the plugins were already injected, causing the newly loaded page to then lose access to those injected plugins. (EDIT: See threads below for the actual reason. It has to do with the plugin-injection code not being permitted on domains other than the start (stub/localhost) domain, unless you add this patch.)

Anyway, my redirect approach is a bit non-standard, so maybe it's not the reason for the issue you're hitting. But I figured I would mention it, since there aren't many google hits for this error message.

EDIT: Oh, I see the issue above (#7467) describes this. And following that chain, there is a also fix/workaround for it here.