Hello Kato,
as written in my first post, we solely use Google sign In (IOS firebase) because our users are managed by Gsuite).
An example of Post is:
-M9nrEuVQmXONztg5LO5 : "Item: diamond \nWhere it was found: here \nEmail:
a...@toto.org"
So we can not use an equality
For the simulator, it won't allow to simulate auth.token.email, but we can see that a rule like:
".validate" : "auth.token.email.matches(/.*@
toto.org$/)" is working perfectly with Firebase (google sign-in). Thus validating that auth.token.email is well populated by your IOS Firebase SDK (Google Sign in)
That is why we can't report you any simulator error (we won't use the emulator at this step as the development is finishing tomorrow)

Hope it is clarifying the context of that technical question
I tried this rule with Firebase Realtime (not the simulator):
".validate" : "newData.val().contains(auth.token.email)"
but it still return False
If there is no way to search for
a...@toto.org within the Post with Realtime, it is fine in the end,
because our app actually does not need this extended check of security
thanks in advance