Skip to content
This repository was archived by the owner on Apr 17, 2020. It is now read-only.
This repository was archived by the owner on Apr 17, 2020. It is now read-only.

Non-local initial discovery doesn't work #140

@nekr0z

Description

@nekr0z

While investigating #139 I bumped into this one, and thought it was worth reporting.

Steps to demostrate and reproduce:

  1. Have Android Studio installed and Android Emulator set up.
  2. Create a new AVD of a known configuration working with ST-lite.
    • Nexus 6P running Android 8.0 (API level 27) should do.
  3. Run the AVD in emulator.
  4. Download fresh ST-lite APK (from F-Droid) and install it in emulator (drag-n-drop works).
  5. Run ST-lite in the emulator.
  6. Manually feed ST-lite and ID of an ST-instance you control and know is running.
    • Your local machine's ST should do.
  7. Wait for however long you feel necessary to persuade you there is an issue, observe "no known address for device" not going anywhere.
    • 17 hours for me, your mileage may vary,
    • optionally, you may force-stop and restart ST-lite several times just for the sake of it; makes no difference.
  8. Download fresh ST-android APK (from F-Droid) and install it into your running emulator.
  9. Run ST-android in emulator. Manually feed it the same ID of the instance you use for testing.
  10. Observe ST-android getting working connection to remote instance in under a minute.
  11. Switch back to ST-lite. Observe it finally getting connection too.
  12. Uninstall ST-android from emulator.
  13. Proceed with your ST-lite debugging as intended.

My point is, steps 7-12 should not be necessary, but I can reliably reproduce the fact that they are.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions