Home | Sign in | English UK
New WINDEV, WINDEV Mobile 25 feature!
  • Overview
  • New "Update 1" features (version 250090)
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Stored procedures
List of new features that you will discover in this upgraded version. Several improvements have been made to this version.
New "Update 1" features (version 250090)
Update required to publish Android applications on Google Play
After each new version of Android is deployed, Google requires a higher target API level ("TargetSdkVersion") to publish applications on Google Play. With the release of Android 10, Google now requires API level 29 to allow deployments. This applies from:
  • 3 August 2020 for new applications,
  • 2 November 2020 for application updates.
This update allows you to generate an application with this API level.
These are the changes that apply to applications:
  1. On Android 10
    • When the application is in the background, it is no longer possible to open a window.
    • It is no longer possible to get a unique device identifier with SysIMEI and SysSerialNum. "Device owner" applications are not affected by this restriction.
    • It is no longer possible to manipulate WiFi connection parameters by programming. The following functions trigger a fatal error when used in Android 10 or higher: WiFiActivate (syntax to modify activation only), WiFiAddNetwork, WiFiDeleteNetwork, WiFiConnect and WiFiListNetwork.
      "Device owner" applications are not affected by this restriction.
    • The content of the clipboard can no longer be retrieved if the application is in the background. In this case, Clipboard will return an empty string.
  2. On Android 10 with API level 29:
  3. The following error may appear when publishing an application on the Play Store: "The private key was not properly encrypted or is not a type of key we support". It is necessary to recreate the signature file of the application (this file can be recreated in the application generation wizard)..
    Caution: If identifiers are based on the signature file (e.g. Google Map identifier), it is also necessary to regenerate these identifiers with the new key.
Management of bar codes
  • PDF417 bar code: If a bar code contained a dash, it could be read as an underscore.
  • In some cases, fReadLine did not read the entire text file.
  • Internal pages: When calling ChangeSourcePage from a page with an independent HFSQL context, the copied context could in some cases not correspond to the desired context.
This version also contains many improvements, optimizations and various corrections.
Minimum version required
  • Version 25
This page is also available for…
Click [Add] to post a comment