Logged_in_customer_id erroneously empty with new customer accounts / app proxy

I’m developing an app that uses an app proxy URL served at <storedomain.com>/a/returns and thus uses authenticate.public.appProxy. This works well, except sometimes the request URL has a blank logged_in_customer_id parameter even when I know the customer is logged in. It’s entirely inconsistent. If I open up an incognito window and log in first, sometimes the logged_in_customer_id will have the proper value on subsequent requests, and sometimes it’s blank. I’ve tried waiting a while to see if it’s delayed, but I’ve found that even coming back hours later, it’s still empty. If I go to /account/login I am shown my account screen with my orders listed so I’m clearly logged in.

Perhaps even worse is that when it does have a proper logged_in_customer_id and then I log out, the logged_in_customer_id still persists.

This only seems to be the case with new customer accounts. Classic customer accounts seems to work fine.

I’d love to turn this into an account full page extension but as that’s still in developer preview I need to know that this functionality will work.

the same here. it’s working fine sometimes. But sometimes on the logout and login flow doesn’t works. The “logged_in_customer_id” param is blank for logged customer.