First, after googling, I saw there was an answer to this 3 months ago in June. However, the circumstances of that have changed, the answer being here:
Back when the discussion was occurring, this was indeed true. Despite having a 64 bit chipset, for some reason Samsung installed 32 bit Android 11 onto the A13 5gs.
However, as per this article:
Around the same time, they added an update to Android 12, which is only available as 64 bit.
I reached out to Samsung support and they confirmed they did not create a 32 bit android 12 out of thin air, and it is indeed running a 64 Bit OS now, but until app creators update their apps for compatibility, they will not function. And I did verify, my a13 5g is indeed running android 12 now.
Now, the Companion App now shows up on the Play Store when you search on the A13 and installs just fine - something that didn’t happen before. (Doubly reinforced by the OP of the linked thread that couldn’t find it in the Play Store) This means that your phone meets the requirements that the app creator (blizzard in this case) set up.
However, despite downloading and installing just fine, it will show the Blizzard Logo, then load the Companion App background, and that’s it. It does nothing after that. This is the screen that it hangs on:
I literally left it on for 2 hours and it never left that screen.
Is there any chance we could get an update on if this might be fixed, or if we’re just screwed, despite them upgrading the phones to 64 Bit?