Update to RC2 broken on a Mac Intel

OS: MacOS Intel

When I click on the update link the updater just flashes for a second or two and quits Wappler. It also uninstalled 6.8.0?

On MacOS Apple Silicon it worked fine

Edit: I updated from Beta to RC2

Same. Mac Intel. Downloading from the Account Dashboard works fine.

1 Like

I had to manually download and install both 6.8.0 and RC2. So now I have both again.

What is going to be the process for updating after final release? Just keep updating 7 or update from 6.8.0? I'm not feeling good about this. :wink:

I'm on Mac Silicon and the auto update isn't working (from rc1 to rc2). It downloads, quits and then does nothing. When I launch it again it's still on rc1.

1 Like

Did it also uninstall 6.8.0 for you?

Worked fine for me on Mac with Apple Silicon processor (RC1 to RC2), 6.8.0 was not uninstalled.

Good point. I hadn't noticed but yes, 6.8 is no longer installed. :frowning:

Well I couldn't find any problems with the inline update/

Seems like you somehow started the update from Wappler 6.8.0, so that is why it removed it.

Anyway doing a full install manually will solve everything.

Maybe I'd suggest to prevent non-Beta to Beta updates

No, that is not the case. I started the update from RC1 to RC2 from the notification link from within the app. I was definitely running RC1 at the time.

1 Like

Same here, was definitely from RC1. I don't ever open 6.8.0.

Same here. I've not run 6.8 this year which is why I didn't notice it had been removed until @brad asked me.

Update: I've now reinstalled 6.8 and installed 7rc2 manually and all is well again.

1 Like

I experienced the same

Fyi, just done update on Windows, no issues.

Same problem here from RC1.
It popped up with a notification giving an error, couldn't take a screenshot before I clicked it away sadly.

I'm on a M2 macbook pro.

When trying to update again and it's giving me this, presumably because the previous broke down and did partly do what it wanted to do

Found the problem. Was indeed a wrong check for beta update while we are in RC stage now.

Will fix it in the next RC, but you will have to manually update to to it, otherwise you will get the same problem, as it is also in RC 2

1 Like

Fixed now in the just released RC 3, but as noted, you will have to do a manual download and install if you are upgrading from a previous RC version.