Unchecking the "Include Configuration App Intent", indeed seems to fix this issue. Since I'm new to this whole widget business, I'm not sure what I'm missing out on, but at least I can now experiment some more. We'll see what errors I run in down the road.

Since last time I visited this problem, I've rebuild my project (since I had not done in 14 years ;-) ). Part of me was hoping that would help, but it did not. What do you mean by adding a static widget target? If that will make the widget run fine, maybe that's a good workaround?

Hhmm. After cleaning the build folder and running again, I am now prompted with the following message: "X will damage your computer. You should move it to the Bin." Apparently, my app is now seen as malware. Don't know if the above "workaround", is the cause of this... Anyone seen this problem, and know how to get rid of it?

I got out of this mess, at least that's what it looks like, for now. I was tired of there being no receipt, so I use some preprocessor flags to disable the exit(173)'s I have in my app. I though let's continue with actual coding... So with that out of the way I could at least run my app again. Because my is going to use a subscription model, I tested if subscribing still worked, and it did! So, I was able to subscribe to my app, and for some reason that added a receipt to my app again. After turning off the preprocessor flags, the app still works, it sees the receipt.