When our production running on Mac 10.15.6 + Safari 13.1.2 the sameSite status seems not right so that we can't keep session data.
Last year we know there is problem on Safari 12.x sameSite.
(not set will become Lax, set none will become strict)
But now it seems this problem still exist in 13.x version.
On Chrome or Firefox we can set none so that our production can run normally. But on Safari the condition seems different.
Now a lot of users using our production+safari is effected by this problem. And believe lots of developer is effected too (https://developer.apple.com/forums/thread/129064?login=true&page=1#624055022).
Just want to know will Apple have plan to handle this???
Can we get any response??
Last year we know there is problem on Safari 12.x sameSite.
(not set will become Lax, set none will become strict)
But now it seems this problem still exist in 13.x version.
On Chrome or Firefox we can set none so that our production can run normally. But on Safari the condition seems different.
Now a lot of users using our production+safari is effected by this problem. And believe lots of developer is effected too (https://developer.apple.com/forums/thread/129064?login=true&page=1#624055022).
Just want to know will Apple have plan to handle this???
Can we get any response??
This Problem have already reported in 2019:
https://developer.apple.com/forums/thread/129064?login=true&page=1#624055022
But no support care ...
https://developer.apple.com/forums/thread/129064?login=true&page=1#624055022
But no support care ...
