Has anyone dared to install IOS18.3?

satchnut

@catherder said:

@pedro said:
Still on 17, why change? Honest question… AI generated emojis? (actually wouldn’t mind learning more about those out of curiosity. How are they sent? How does the receiver device display them?)

Agree. I will stay on 17 until there is an app that I want and that makes an upgrade worth it. Otherwise AI stuff and makeup don’t interest's me. In contrast a better, less crippled browser or a free choice of browser engine would be a reason to upgrade.

Safari has been steadily breaking more and more through the past handful of iOS updates. (for me at least)

Littlewoodg

@Edward_Alexander said:

@Littlewoodg said:

@Edward_Alexander said:
Thor is the one synth app I always think about when deciding to update or not. So far, it still works amazingly well with 18.2.1

Seeing your post encouraged me to open this one up again. Extraordinary synth, I still haven’t plumbed its depths in all this time…

Are you using it in a DAW? I’ve tried playing around a bit with my go-to DAW, still problem solving trying AB3. Are you having success with an approach?

I’ve had success using it with Loopy Pro, along with a few other IAA synths like Shoom for example.

It also still works great with AUM.

Thank you. This gives me further encouragement

I did find a workable approach in MTS, which was slotting it in directly as IAA and using that DAW’s routing to record audio.

In that use-case to stay in the DAW gui to play in sync with my other tracks I needed a MIDI keyboard.

Not sure that sending midi from MTS tracks actually works. (Still fiddling) Sounds like you are able to program midi from your DAW tof F send to Thor with your set up.

And to unhijack the thread, I haven’t updated my Air 4 to 17. I froze there because 17 and 18 broke some of the same favorite apps on my phone which I do keep current.

busaudio

@wim said:
After checking further, maybe I assumed wrongly. I see several posts out there that downloading on iMap servers is broken for some even though they can demonstrate that authentication is happening. Without details as to whether authentication and sending email is working I can't opine whether its a server side or client side issue.

On the other hand, I use iMAP with iOS 18 and am having no problems. I would also expect this to be a lot more widely discussed if it is a general problem.

I invested some time into this.

From some websites and forums, it indeed seems to be required to use a certificate with a SAN record.

I used the following commands:

# CA key:
openssl genrsa -aes256 -out ${CA_KEY} 2048

# CA cert:
openssl req -x509 -new -nodes -key ${CA_KEY} -sha256 -days 3650 -out ${CA_CERT}

# Server key:
openssl genrsa -aes256 -out ${SERVER_PRIVATE_KEY} 2048

# Remove the password for use on the server
openssl rsa -in ${SERVER_PRIVATE_KEY} -out ${SERVER_KEY}

# Copy private key to SSL folder, as root:
chgrp ssl-cert ${SERVER_KEY}
cp ${SERVER_KEY} /etc/ssl/private/${SERVER_KEY}

Then create the SAN record from the domains in question:

# Start with the CN, which normally is the primary domain:
SAN="subjectAltName=DNS:${CN},DNS:www.${CN}"

# All all others, including wildcards:
for d in ${DOMAINS[@]} ; do
        SAN="${SAN},DNS:${d},DNS:*.${d}"
done

# Create the CSR:
openssl req -new -nodes -key ${SERVER_KEY} -subj "/CN=${CN}" -addext "${SAN}" -out ${SERVER_CSR}

# Server cert:
openssl x509 -req -in ${SERVER_CSR} -CA ${CA_CERT} -CAkey ${CA_KEY} -CAcreateserial -days 365 -sha256 -extfile <( printf "[v3_ext]\n${SAN}\n") -extensions v3_ext -out ${SERVER_CERT}

# Copy the CA cert and the server cert to the certificate folderl, as root:
cp ${SERVER_CERT} ${CA_CERT} /etc/ssl/certs/

# You can also "cat" those two cert file and add them as /etc/ssl/certs/${CN}.pem
# But I had problems with such a PEM file on the iPad and tested with separate files instead.

# Update CA certificates:
update-ca-certificates

Make sure that IMAP (dovecot) and SMTP (postfix) are pointing to both key and certificate, then restart both.

After that, first add the CA cert to your iPad or iPhone (by mail or from some file system in the Files App).
This requires adding it in the settings App too and afterwards, you need then to trust the CA cert (Settings / General / About).

As second step, add the server certificate - again over mail or the Files App, then add it in the settings App. I did not need to trust it.

After that, you can add the mail account again in the Settings App and use it afterwards with the Mail App.

That worked for me - also on iPadOS 18.x

EDIT: I added a comment about a ${CN}.pem file from "cat ${SERVER_CERT} ${CA_CERT} > ${CN}.pem"
That should work for the server, but I had problems on the iPad and used two separate files for the iPad.

wim

Thanks for taking the time to post all that @busaudio !
I hope I remember where to find it when someone posts about the problem later on.

Certificate issues hurt my brain. Every time.
Except for Caddy server for reverse-proxy web traffic, where it's all taken care of for me.

busaudio

@wim said:
Thanks for taking the time to post all that @busaudio !
I hope I remember where to find it when someone posts about the problem later on.

Certificate issues hurt my brain. Every time.
Except for Caddy server for reverse-proxy web traffic, where it's all taken care of for me.

Yeah, I hate them too - esp. as Apple makes it hard to handle them, compared to other OSes.

I can finally update other devices too :-)

Note, that I edited the first version!

busaudio

I noticed a strange change in the colors of widgets (those that you can swipe in from the left).

On iPadOS 17:

Now it looks ugly to me:

No idea why and how to fix this.

But yes, this is not crucial.