The dreaded deadline has come back again.
Can somebody please confirm if they have moved to api version 35 from meteor 2.x
I have yet to upgrade my app to 3.x and it is proving be a slow and laborious process.
4 Likes
I didn’t succeed. 
I tried everything, but it won’t work.
The problem is that API 35 requires Java 17.
I switched to Meteor 3.2 and Capacitor, but I still have a lot of problems with creating native files (for both Android and iOS).
In the end, I will probably switch to pure JavaScript and capacitor because my application doesn’t have a server part. I’ll port Blaze to Handlebars and that’s it.
We’re aware of this and plan to release Cordova Android 14.0.0 for Meteor 3.3.1 soon (beta coming shortly). It adds support for Android API 35. With this update, you should be able to upgrade your Meteor 3 app and publish successfully to the app stores.
Support for Meteor 2.x will arrive later 3.3.1 if supported. We can’t guarantee it will work with Meteor 2.x apps because the new Cordova updates require Node 20+, whereas Meteor 2.x uses Node 14.x. It may remain compatible as previous updates, but we can’t be certain. We’ll try our best, but as time goes by, it becomes harder to sort this out.
Migrating to Meteor 3.x is increasingly urgent for native development. Cordova now requires specific Node versions, which could soon block Meteor 2.x users. Also, we will end maintenance on Meteor 2.x in December 2025 to focus on Meteor 3.x and future Capacitor integration.
3 Likes
Thanks @nachocodoner
Is the plan to have a seamless migration to capacitor or is it going to be a breaking here as well.