Skip to main content
CDohrn
Participant
June 20, 2024
Solved

EOS and AppLab - login issues with DeviceID

Hi! I'm developing a multiplayer application for Meta Quest that uses Epic Online Services (EOS). The users are supposed to login using DeviceID. This login method used to work perfectly when I submitted the app to the Alpha Channel of AppLab. Since a few months, the same application in AppLab is not able to login using this method anymore. The login fails silently and doesn't provide any error message. But when I install the application locally on my Quest, without submitting to AppLab, the login works fine. So, I suppose that there is something different or new in AppLab regarding this login method. Does anyone have an idea of what could be wrong or how to solve the problem?

This topic has been closed for replies.
SeguyoyAnswer
New Participant
July 15, 2024

android:allowbackup= false didn't work for me, disabling the quest device cloud storage did work, however someone else in my team figured out we could disable the cloud storage of the app from the app lab page so we didn't have to disable all cloud storage on the device.

View in thread

9 replies

Aymito2
Up and Coming
June 26, 2024

you could try to update meta xr plugin, or update the quest sdk, did you do that with a special plugin, or normal eos setup I am just curious to know.

    CDohrnAuthor
    Participant
    June 29, 2024

    Thanks for the suggestions! I wasn't using the Meta XR plugin. But I'll try enabling it and also updating my Quest SDK. I'm actually using the EOS Integration Kit plugin, from the Unreal Marketplace.

    Seguyoy
    New Participant
    July 4, 2024

    did you manage to fix it? I'm also using the EOS integration Kit Plugin and I'm having the same issue, works fine without applab but not  in applab

      CDohrnAuthor
      Participant
      July 4, 2024

      Sorry. I still haven't got the time to test it with an updated SDK and Meta XR plugin. I'm also expecting the version 4 update for the EOS integration Kit Plugin to see if it makes a difference. I'll post here the results once I test it.

        Starkium
        Up and Coming
        July 10, 2024

        I'm using the redpoint version of EOS and I think I've also recently had issues with. I'll test again shortly. 

        Bringing games to Life
        Seguyoy
        New Participant
        July 10, 2024

        I think I found the issue, its hard to explain but applab has a cloudstorage option that makes a backup of the app when you uninstall it and then re-install it, this messes with the plugin device id login method so after disabling it and uninstalling and reinstalling my app it was working fine. This was the error that I found while debugging if you want more info https://stackoverflow.com/questions/55665337/keystoreexception-signature-mac-verification-failed-when-trying-to-decrypt.

          CDohrnAuthor
          Participant
          July 12, 2024

          Thanks for the explanation! I've tried adding android:allowBackup="false" to the extra tags for <application> node of the Advanced APK Packaging in Unreal, but it still didn't work. Then I've disabled Cloud Backup inside my Quest, uninstalled and reinstalled my app and it started working fine with the login. Did you manage to make it work just with android:allowBackup="false" or you also had to disable Cloud Backup inside Quest? 

          SeguyoyAnswer
          New Participant
          July 15, 2024

          android:allowbackup= false didn't work for me, disabling the quest device cloud storage did work, however someone else in my team figured out we could disable the cloud storage of the app from the app lab page so we didn't have to disable all cloud storage on the device.

            CDohrnAuthor
            Participant
            July 15, 2024

            Thanks Seguyoy! I've also disabled the cloud backup for my app in the AppLab page and the login is working fine now.

              Terms & ConditionsAccessibility statement