Dan G

When/if he gets round to it Emlyn will have to create the 2 new certificates and follow the guides as mentioned in the description. Apple doesn't make this easy enough...

I'm seeing this issue now, when trying to run a Universal (Intel+AppleSilicon) app built using Qt 6.3.2, running on an intel MacBook. When I run the app from the terminal...

I also don't have access to an M1 machine. I can help debug this use case (running a Universal build on intel mac) but I don't have project bandwidth or...

Is it necessary to actually have a physical M1 mac, if I can reproduce the error by running the Universal build on intel? Otherwise is this a Won't Fix scenario?...

> I - apparently - have access to an M1, what would be required to reproduce this? The universal build that fails for me on Intel will probably also fail...

@Shirk Maybe the simplest reproduction would be if you ran the simplest example in QtCreator: https://github.com/itay-grudev/SingleApplication/tree/master/examples/basic If that works/fails that would provide a good baseline for debugging :)

> Update - more research - still not QSingleApplication's fault; Qt has a number of "specialities" for Apple & the Mac AppStore: I don't need to do any of that...

@itay-grudev Seems like @Shirk has isolated the issue, has an M1 Mac and is willing to run test builds :) Do we have the elements to potentially implement a fix?

> Just one question - is the `` something Apple assigns developers or could it be arbitrary? I'm not 100% on this - but I think the `application group identifier`...

Many thanks @Shirk - this is indeed very helpful. I'll go ahead and create the Application Group as advised. > There's no way - I'm aware of - for QSingleApplication...