Authentication Errors for Storage on iOS

[timrach]

Hi, I was wondering if the '@capacitor-firebase/storage' package needs additional configuration on iOS.
Storage access works fine for Android users, but on iOS I get 403 errors for up- and download requests.
It shouldn’t be a configuration error since accessing storage with the 'firebase/storage’ package works fine on iOS in the same app.

[robingenz]

In this case the error should lie in your Android configuration. Make sure the plugin is correctly installed on Android and that all configuration files (including Firebase json) are up-to-date.

[timrach]

I already did that, but I understand the symptoms hint towards a misconfiguration.
I probably missed something or did it wrong. I’ll do it again and see if it fixes my problem.
Thanks!

[timrach]

Hi! I i finally figured out how to solve my problem.
Hi! I got a bit closer to a solution:
I suspected that it must have something to do with the FirebaseAuthentication plugin since I also got the Runtime error described in #925. But since my general authentication flows worked fine it was hard to find. I wanted to see if it might be a problem with Apple or Google sign in and did setup email/password authentication. The Login worked fine and also storage access was successful. I also noticed that when I have an active session with email/password, the next time I run the app, the RuntimeError message disappears

[timrach]

Hey @robingenz I just saw the note in the auth package that when using apple sign in combination with the js SDK, we have to provide skipNativeAuth: true. Does that mean I cannot use the @capacitor-firebase/storage package (which I suspect needs a user to be authenticated on the native layer) with Apple Sign when also using the JS SDK?

[robingenz]

@timrach That‘s True. We recommend to only use the native SDKs.

[timrach]

Ok thank you that resolves my initial problem. May I suggest that this is made a bit more prominent in the package README files?
I know there are hints and links towards the JS SDK specific document but in there the relevant note is a bit hard to find.
At least it took me quite a while to understand what was the problem in my ionic app, then find the note and make the connection.
Again, thanks for your super quick help! 🙏

[robingenz]

@timrach Yes, we definitely need to improve our docs on this. Thanks you for the feedback! I will try to add this in the next few weeks.