Skip to main content
W
Warsha Everything Mobile
Documentation / BLE Studio / Android / Version 1.1.2
Browse documentation

Releases

Included with Warsha BLE Studio for Android

v1.1.2

Version 1.1.2

Your Recent list survives a restart, an update the app requires stays required until you install it, and the app tells you why when something does not work.

Changes since 1.1.1

  • Recent is kept. The targets you ran recently are still listed after you close the app, restart your phone or update the app. Before, the list started empty every time.
  • Required updates stay required. Once Google Play has confirmed that a required update is available, the update screen stays after you close and reopen the app, including without a connection.
  • Update now always responds. If Google Play can’t start a required update from inside the app, Update now opens the app’s page in the Play Store instead of doing nothing.
  • A withdrawn version stops its peripheral. If the version you are running is withdrawn while a peripheral is running, the peripheral stops. Maintenance and required updates still let a running session continue until you stop it.
  • Going back to an older version. If you install an older version over a newer one, the app now opens normally. Settings you change last until you close the app, and the log says so.
  • Failures say why. Importing, exporting or sharing your library, starting the Remote Script Editor, and running a target, preset or device now tell you when they did not work and why. Before, most of these failures only reached the session log.
  • Clearer purchase messages. When a purchase, restore or subscription change can’t complete, Plan & Billing names the reason, such as no connection or purchases being restricted on this device. A purchase that can’t be verified asks you to check the date and time instead of saying Google Play is unavailable.
  • Script permission requests. If a script changes while it waits for your permission, the app tells you to run it again instead of closing the request without a word.
  • Remote Script Editor pairing. An incomplete pairing code is caught before it is sent, so it no longer counts as a wrong attempt, and codes typed with Arabic or Persian digits are accepted.

Known limits

  • The Remote Script Editor is unencrypted and is for trusted networks only.