Closed JTCorrin closed 1 year ago
I have the same issue, but with Supabase Auth...
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 💙
An alternative here if you're not needing to proxy all of the requests (which if you're using something like firebase or supabase you probably don't want to proxy everything), is just to only use Capacitor HTTP directly for the specific requests instead of enabling the proxy and patching fetch/xmlhttprequest https://capacitorjs.com/docs/apis/http#example
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 💙
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out.
Bug Report
Capacitor Version
Platform(s)
iOS Android
Current Behavior
The addition of
to capacitor.config.ts stops/blocks/makes fail Firebase from making firestore calls in my app. Removing the above config resumes normal behaviour
Expected Behavior
firebase should continue working as normal
Code Reproduction
I've a bunch of firestore calls which look something like the below in my app. They don't seem to work
Other Technical Details
npm --version
output:node --version
output:pod --version
output (iOS issues only):Additional Context
Lots of errors that looks something like this on both iOS and android:
I can see the "internet connection" suggestion in the error output there but that is not an issue.
I'd simply remove http but I believe I need it to get capacitor-community/background-geolocation working (to make http calls from the background)