It’s difficult to debug such things remotely, some notes:
I’ve used both Authorization: Bearer XXXXX and apikey: XXXXX headers in my settings
Never heard about Adalo stripping anything
Testing connection and using External collections’ in the app work differently. When you test the connection, it is done via a certain endpoint (https://backend.adalo.com/test-api-endpoint). But actual app (be it a preview or a published app) works through a different server (not from your app but Adalo one).
I would have looked at RLS (disabling it completely) but it is unlikely it causes an issue.
the test connection in External collections work fine, and
when you create a native app build in Adalo (Android or iOS), it works fine,
but when you run a preview from the Adalo builder, it doesn’t work, and
when you open the PWA (published one), it doesn’t work as well?
That’s quite a strange case, and given my knowledge on how Adalo External collections work, I can’t imagine such case (queries to External Collections come through Adalo server anyway, both from PWA and native builds).
As I have mentioned, it is quite difficult do debug such issues remotely, given 0 screenshots, logs, and screen recordings. Even with this info, some hands-on tests are needed. Therefore I would advice to submit a support ticket New Bug Form so that Adalo Support can have a look directly at your app.