updater doesn't work on MacBook Pro M1

dispausible

What’s the issue?

My Reliq arrived today, pristine 1.0.0. Updating to 1.2.0 doesn't work.

How to reproduce

Downloaded Reliq updater on my MacBook Pro M1 and placed the app in the applications folder.
After starting the app it sees the Reliq connected. Pressed UPDATE
Downloaded the update file, works fine.
File transfer begins. Reliq displays 'waiting for the update file to arrive'
Updater displays 'File transfer complete'. Reliq display doesn't change and still says 'waiting for the update file to complete'.

System info (if relevant)

Rlx version: 1.0.0
Connected devices: none, besides MacBook Pro m1
DAW or software used: none
Platform: Mac

Screenshots or videos (if applicable)

Include links or uploads if visual context would help us understand the issue.

mikeleebirds

Updating does not work on my Mac M3, even after trying a bunch of things suggested by tech support. I always get an error message that transfer to my Reliq did not succeed, so at least you are one step further. :-)
I had to borrow a Windows computer to update my Reliq.

I'm curious if there will be a solution for your situation.

liradigital

The update is a little bit tricky. In my Mac mini M1 only works with the supplied usb cable and all the other Mac usb inputs disconnected. I would need a longer usb cable.

dispausible

I managed to update my Reliq to 1.20! Not quite sure what I did differently, but maybe the updater just doesn't work on Sundays ;-)

In case this helps anyone else:

I used the supplied cable with a USB A --> USB C adapter on my MacBook's side, and the MacBook running off its internal battery.
I started up the updater app first, and only then the Reliq. I didn't touch any buttons or encoders.

Yesterday I first got a few errors somewhere along the transfer process. After a few tries, the file transfer seemed to succeed, but the Reliq stayed frozen on the 'waiting for the update file to arrive' message. Today it just worked. Strange but true.

giu_reliq

Hey @dispausible, sorry for the trouble, but glad it’s all sorted now 🙂
Looks like the main bottleneck was the cable: we recommend using a USB-C → USB-A cable for updates. Using an adapter or USB hub in between is totally fine too

If anything else comes up, just shoot me a message!