This is a milestone for all dedicated developers who have believed in Meteor from the start, consistently providing solutions and achieving significant accomplishments both individually and collectively, by offering worthy software to companies and users. It is also an opportunity for others to join in and continue improving Meteor.
Thank you to all Meteor team and community! Special thanks to technicians @denyhs and @grubba, whose hands-on work and years of commitment and patience have helped shape Meteor into what it is today with Meteor 3.0.
This is a huge milestone and just the start of innovations and upgrades that Meteor.js needs.
Thank you to everyone who helped us, especially the Core team members.
A huge thank you to all who contributed to the effort especially @denyhs, @grubba, and @nachocodoner for all their hard work. And of course @zodern for their key contributions and guidance.
I want to say a big thanks to the community; without the support, testing, pinging, and question-asking, we would not have been able to get through it.
Since Monday, I’ve been solving some things for the release, so I didn’t take time to post anything here besides a GIF
I’ve been part of this process from start to end, literally. It was a crazy ride and a pretty tiring one. And there were some moments I needed to take a step back to breathe. Otherwise, I couldn’t continue. But I continued because I had full support from the community and, especially, from the core team, which always understood how massive this project was and how much it could take from someone.
So, I want to thank you all for your hard work and help over those two (three?) years.
It’s really amazing to see what we accomplished together as a community.
The work isn’t done yet, but now Meteor will thrive towards a bright future
What’s the status of Cordova? Getting in to run on iOS used to work without any configuration (well except for the certificate in Xcode). Have not got it to work with Meteor 3 yet.
I’d like to know for Meteor-Desktop as well. We’re many full versions behind due to the existing limitation of NodeJS on Meteor 2.x - will you be working on migrating it to 3.x and pushing all dependencies @storyteller ?
Did these problems occur in any existing Meteor 2.x project during the transition to Meteor 3.x?
If so, it might be an issue with your specific configuration, setup, plugins, or package incompatibilities with latest Node somehow, since nothing around Cordova deps was changed on Meteor 3.x. The new Node.js version used for compilation could cause different building of native dependencies, requiring adjustments.
Whether it’s a new app or a migration, please point me to the GitHub issue where you describe the problem and the reproducible steps so we can assist you.
I have tried running a fresh meteor create app on iOS and that’s working. Figuring, what’s wrong with my actual app is pretty hard, because I do not get any error logs from the cordova app. I don’t get any console.logs from the app at all. The problem must manifest before meteor startup.
Found another problem with Safari on iOS and dynamic imports when connecting to the dev server.
When I access the app from the deploy on digital ocean it works fine. When I access the same app from the dev-server It crashes as soon as It get’s to react components that are lazily loaded with dynamic imports. It’s working fine with both safari and chrome on my Mac either way.
Meteor.settings is not defined on iOS builds. That’s what was causing the problems. Just a white screen with no error message of any kind. Took me a hole day to figure out. Problem also happens when you actually have a settings file. Meteor.settings seems completely broken on ios
Hi, without any further checking, just a quick info: I built our app on Meteor 3.0 + iOS last week, and it probably hat its settings or nothing would have worked.
We’re using an explicit --mobile-settings ./mobile-settings-live.json for the build though.
Also another settings package to be able to have default settings (ogourment:settings@0.1.4)
I’m not sure under what circumstances this issue arises. Does it occur in dev mode, when loading locally after meteor build, or when deploying to iOS production?
I tested on my end and found that using Meteor.settings or the settings.json file works for both the skeleton and simpletasks projects, in dev mode.
I suggest removing added native plugins and meteor packages and code related from your project incrementally, running the app continuously until it stops crashing. Then, try to replicate the issue in a small, reproducible example that we can examine. Since other developers aren’t encountering this issue in iOS, it seems specific to your setup. We need more information to find the proper solution.
Sorry to hear that, can you provide more information that might lead to what specifically is causing it? Me or @nachocodoner will reach out to you to help understand it better.
Hard to say for sure. I was able to capture a CPU trace using monti APM, but I can’t pinpoint to anything in particular. The only wierd things in this trace are:
out of 10 captured seconds, 700ms are spent in cookie parsing.
a lot of time is spent on garbage collection, even though the container was using 1.5GB out of 4 available in container
