[Bug] iOS Storage reads are never Auth'd

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2019.4.28f
• Firebase Unity SDK version: 8.1.0
• Source you installed the SDK: .unitypackage
• Problematic Firebase Component: Storage
• Other Firebase Components in use: Auth, Database, Firestore
• Additional SDKs you are using: Yodo1, Megacool
• Platform you are using the Unity editor on: Windows + Mac
• Platform you are targeting: iOS, Android (issues happening on iOS)
• Scripting Runtime: IL2CPP (Mono, and/or IL2CPP)

[REQUIRED] Please describe the issue here:

In our current project, we are using a mix of both Firestore and Storage to create a UGC browser. However, on iOS Storage reads always returns the error Error Code '-13021' 'User' is not authorized to perform the desired action. Even though we have no problem writing to our storage with the exact same check allow read, write: if request.auth != null. Similar rules setup on firestore have no issues running and succeed.

Here’s the setup with a Repro project

• Storage Rules
• Firestore Rules
• Results we get from our tests

Steps to reproduce:

What’s the issue repro rate? (eg 100%, 1/5 etc) 100% Reproduction rate

What happened? How can we make the problem occur?

1. Setup a project which will download anything from storage. Can be an image or whatever.
2. Setup your security rules for reading from the database to check if the user is Authenticated request.auth != null
3. Authorise the user with any kind of Authentication method. For the repro, we use anonymous authentication.
4. Make an iOS build to test on. [Editor + Android works as expected]
5. Once authenticated attempt to download anything from the storage.
6. Note that you get an error noting that the user is not authorized to perform the action. However we should be allowed as the rules allow authorized reads, and the file on the server exists

I’ve attached a repro with more in-depth instructions which is already set up here.

Let me know if I’m missing anything or need to make anything more clear. Cheers, Chris.

[a-maurice]

We’ve released a new version of the Firebase for Unity SDK, 9.0.0, available here: https://github.com/firebase/firebase-unity-sdk/releases/tag/v9.0.0, that includes the fix for this.

The problem seems to have been in how the C++ SDK was interacting with the iOS SDK, but the iOS SDK was rewritten into swift, so there isn’t a PR on the Unity side that reflects the fix, but from personal testing, I wasn’t able to reproduce it after updating. Thanks for flagging this, and sorry it took a while to fix.

[a-maurice]

Hi all,

We’ve been struggling to reproduce this issue (including the repro case that you’ve provided). We did recently ship a new version, 8.9.0, which contains a fix to EDM4U, the tool we use to manage iOS dependencies, to properly handle source Cocoapods. I’m not sure if that will resolve the problem though, as we haven’t been able to reproduce it on older versions either.

To confirm, this only seems to be happening on Read, not on Write?