Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App put in background not reconnecting to AltServer after put back on focus and popup still showing Connected... #1487

Open
iulianatodoran opened this issue Jan 23, 2024 · 2 comments

Comments

@iulianatodoran
Copy link
Collaborator

iulianatodoran commented Jan 23, 2024

Prerequisites

  • ❗ On the Android/iOS device make sure to have the option Battery saver/Power saving selected

Steps to reproduce

  1. Start the AltServer from AltTester Desktop in batchmode
  2. Open a mobile instrumented build with matching connection data
  3. After the connection is established, put the app in the background
  4. Wait 4 minutes until the app disconnected from the AltServer (check the logs)
  5. Bring the app back in focus and check the connection status on the AltTester Popup and the AltServer logs

Actual result

AR

After the app is brought back on focus, the AltTester popup shows that the app is Connected... but with the old appId for the former connection with the AltServer and the AltServer logs show that the app did not reconnect.

Additional info

Environment

  • sampleGame Android/iOS build instrumented with AltTester Unity SDK from development branch (23.01.24)
  • AltTester Desktop from development branch (22.01.24 - commit 341ccc1)

Screenshots
image

Other notes

Expected result

ER

After the app is brought back on focus, the AltTester popup should show that the app is Connected... with a new appId for the new connection with the AltServer and the AltServer logs should show that the app reconnected.

Additional info

Testability

@RobertPoienar
Copy link
Contributor

Triaged Week no. 5, 2024. Not prioritized for next releases.

@iulianatodoran
Copy link
Collaborator Author

iulianatodoran commented Apr 22, 2024

Still reproducible with v 2.1.0 but after this version changes the AppId is expected to remain the same until the connection data is restarted.

@gomboskriszta15 gomboskriszta15 added this to the Concurrency milestone Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants