Skip to content

Joining probe wifi for network ID when clarius app is running does not work the first time #75

@jspanchu

Description

@jspanchu

Describe the bug
As @julien-l suggested in clariusdev/cast#175 (comment), we use code similar to https://github.com/clariusdev/solum/tree/master/examples/solum_android/app/src/main/java/me/clarius/sdk/solum/example/bluetooth in order to get the "networkID" parameter in a network callback. We noticed a buggy behavior in the solum_android example that happens only when the clarius app is running in the background and already connected to the probe. The first request to join the wifi doesn't invoke the network callback. Instead, the request needs to be made a second time in order for the network callback to trigger.

Since we use CastAPI, we require Clarius App running in the background. This bug can be reproduced by following the steps below.

To Reproduce
Steps to reproduce the behavior:

  1. Launch Clarius App on an android device.
  2. Find a probe and join the probe's wifi.
  3. Launch solumn android example - https://github.com/clariusdev/solum/tree/master/examples/solum_android
  4. Tap "BLUETOOTH"
  5. Select the same probe as step 2.
  6. Tap "CONNECT"
  7. Go back
  8. Tap "AUTO JOIN WI-FI"
  9. The "Network ID" field is blank, nothing happened.
  10. Tap "AUTO JOIN WI-FI", again
  11. The "Network ID" field is now populated.

Environment:

  • Development platform [e.g. Linux, Xcode]: Android
  • Clarius App version: 12.0.2-631+f8b5d0a851

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions