Fixing Google Play target API failures for Expo apps (temporary workaround + permanent fix)

What happened (the issue)​

Google Play now requires apps to target recent Android API levels. Starting in late-2025 new submissions must target Android 15 (API 35) and existing apps must target at least Android 14 (API 34) to remain available to new users on newer devices. If your build is still targeting an older API level, Play will either reject uploads or progressively limit availability on devices running newer Android versions.

Temporary (immediate) fix — update app.json​

You can temporarily force the Android compile/target SDK versions via the expo-build-properties config plugin in your app.json. Upload the following app.json into studio -> src/main/webapp (or commit it to your repo) so the build system picks up API 35:

{
  "expo": {
    "plugins": [
      [
        "expo-build-properties",
        {
          "android": {
            "compileSdkVersion": 35,
            "targetSdkVersion": 35
          }
        }
      ]
    ]
  }
}

Reference: https://docs.expo.dev/versions/latest/sdk/build-properties/

When will this be permanently fixed?​

This will be resolved in coming release with expo 52 to 53 stack upgrade

When working with React Native Studio projects, it’s important to ensure that your Node.js version aligns with specific requirements for different stages of the development process. Here’s a breakdown of the required Node.js versions for building the project and running a local preview.

WaveMaker is a scalable accelerator platform that enables developers to rapidly build enterprise-grade applications with minimal coding while maintaining control over the generated code. Unlike other low-code platforms, WaveMaker allows developers to hyper-customize components and seamlessly extend functionality.

WaveMaker generates reusable Angular code that follows best practices, such as:

• Component-Based Structure: Each page is generated as an Angular component with an isolated scope.
• Security & Performance: Auth guards, tree-shaking, and minification are applied to keep the code efficient and secure.
• Custom Extensions: Developers can add custom or third-party Angular components to extend the generated ones.
• Easy Deployment: The frontend code can be deployed separately as static assets to a CDN.

This document guides you on running, editing, and extending the generated Angular code for the web after detaching it from WaveMaker Studio. It also outlines our roadmap for improving this experience.

Web Components are a modern web standard that enable the creation of prebuilt, reusable, and encapsulated custom HTML elements. These components are completely framework-agnostic, making them compatible with any application, whether it's built with Angular, React, Vue, or plain JavaScript. They provide several key advantages:

• Framework Independence: Designed to work across different JavaScript frameworks and vanilla web applications
• Native Browser Support: Leverage built-in browser technologies
• Encapsulation: Provide strong isolation of styles and functionality
• Reusability: Create components that can be easily shared and integrated

In today’s rapidly evolving digital landscape, security remains a cornerstone of application development. With the release of WaveMaker Studio 11.10, we are thrilled to introduce a game-changing feature—the ability to configure multiple security providers for your applications.

This feature empowers application developers to seamlessly enable and manage multiple security providers, offering greater flexibility and enhanced security for their applications.

Why Multi Security Providers?​

In an increasingly diverse tech ecosystem, users interact with applications through various authentication methods. Some organizations rely on traditional database-based authentication, while others prioritize enterprise-grade solutions like LDAP. Additionally, social logins such as Google and LinkedIn are becoming more popular for their ease of use.

With the new multi-security provider support, WaveMaker Studio empowers application developers to integrate and configure multiple authentication methods tailored to their application’s needs. This flexibility ensures enhanced security and a seamless user experience.

How often do you visit the documentation site?

If you're someone who loves (or is forced to) diving into the docs for answers, you’ve probably noticed a few things look… different. And if you haven’t been back in a while, no worries – this blog is here to catch you up on everything you’ve missed. We’ve been working on docs behind the scenes, and now it’s time for you to explore what’s new.

WaveMaker Studio 11.10, scheduled to release on 27th January, brings a range of powerful new features, design capabilities, stack upgrades, and enhancements to improve your app development experience. With this release, we’re introducing groundbreaking capabilities like Exporting Prefab as Web Component for building framework agnostic components, and a Project Migration Report, while also upgrading our technology stack to ensure your applications remain modern, secure, and future-proof.

This release also focuses on future-proofing your applications with upgrades to Angular 18 for Web Applications and Expo 52 for hybrid mobile applications, ensuring they remain secure, performant, and aligned with the latest industry standards.

Additionally, we’ve made several enhancements and restructured Docker configurations to improve maintainability. Alongside these updates, we’ve resolved numerous bugs to ensure a smoother development experience.

Building and deploying modern applications often comes with its fair share of challenges, especially when dependencies and configurations differ between versions.

For example, Angular applications require a specific Node.js version to match the Angular framework version. Upgrading from Angular 17 to Angular 18 might necessitate updating Node.js and npm, causing disruptions in the development process.

WaveMaker applications are no exception.

Developers frequently face hurdles like managing varying Node.js and npm versions, upgrading build environments, and ensuring secure and optimized deployment configurations for application servers like Tomcat.

To address these pain points, we are excited to introduce a set of Docker images for building and deploying WaveMaker applications. These Docker images streamline the development and deployment process, reducing friction and allowing developers to focus on what they do best — building great applications.

At WaveMaker, we are committed to providing a seamless and modern development experience for our users. As part of this commitment, our low-code studio integrates with various database providers to offer robust Database Services for the applications you generate. Staying in sync with the latest advancements in database technologies ensures your applications are secure, performant, and future-proof.

In our latest release, we’ve upgraded the supported database server versions, phasing out deprecated versions and aligning with the industry’s best practices. Here’s everything you need to know about the changes and how they impact your applications.

At WaveMaker, we're committed to ensuring that your applications are always powered by the latest and greatest technologies. As part of this commitment, we’re excited to announce that the upcoming WaveMaker Studio v11.10 release, scheduled for January 27, 2025, will transition all generated web applications to Angular 18 and Node v22.

Angular 17, the backbone of current wavemaker's web applications, is set to reach its end of life on May 15, 2025. To keep your applications secure, performant, and future-proof, we’re making the proactive move to Angular 18.