No. You have developed an app that you want to put on the App Store, and it is currently being rejected until you implement the things the App Review team have told you to do. How would we be able to help you? You've got the code, not us. You need to figure out how to add those features.

"I also reported this issue on feedbackassistant, but I didn't get a response from the feedbackassistant" What do you mean you didn't get a response? Do you mean Feedback Assistant didn't work, or no one replied to your bug report? No one is going to reply to your bug report unless they need more information from you. You don't need to duplicate your bugs, and this is not the right place to put them.

Just ranting to myself since barely anyone responds to my questions on here. I can't get Family Sharing to work properly. If I purchase on one device in one sandbox account, it doesn't appear on the other device in the other sandbox account unless I kill the app and relaunch it. The listener task (taken from the FoodTruckBuildingASwiftUIMultiplatformApp sample code) doesn't seem to actually trigger at all, and it's not obvious how to get it to trigger. The Developer session videos for StoreKit2 say to listen for transaction updates on app launch, but the sample code (mentioned above) doesn't do anything of the sort. Honestly, I wish Apple would provide sample code that does ONE thing at a time, and has comments in it. Not everyone is writing an app that has every type of in-app purchase, so some sample code that shows non-consumable purchases would be great. Then another showing consumables. Then another showing subscriptions, etc. By all means put it all together in one app, too, but help us out here! When you bunch everything into one sample app it becomes extremely difficult to follow what's going on, and if we have to cut out the bits we don't need, how do we know we aren't removing something we actually do need? It gets so frustrating trying to write code for Apple's platforms. I'm not stupid, I write code all day, but some of this stuff is so poorly documented that it drives us away from these platforms.

Are you telling us there's a bug, or are you asking for help? If you're telling us there's a definite bug, then you need to post it in the usual place: https://feedbackassistant.apple.com/

Post some properly-formatted code here and we might be able to help you. Right now, all you've done is tell us you have a problem. We can't really point you in the right direction without seeing where you're going wrong.

A beta release is a version of software that is currently in development, which might be why you're experiencing bugs. Maybe they're caused by the beta, maybe they aren't. However, macOS 15.3 is now at Release Candidate stage, which means the final release to the public will be in the next few days or week. If I were you, I would turn off beta updates, and wait until 15.3 is released to the public. It's easy: Open System Settings. Click on General. Click on Software Update. Click the i beside Beta updates and make sure it is set to off. Now that you're no longer in the Beta program, the next version of macOS you'll see in System Settings will be 15.3.

Start a new project - iOS App - give it a name, choose SwiftUI as the interface, and Swift as the language, and tell it where to save it. If you choose a storage option other than None you'll have a working app with a backend data store. App.swift file is the main entry point to the app you're building, and ContentView.swift is called by App. ContentView() is your SwiftUI view where you can start to build your interface. You don't need to use storyboards anymore (thankfully). SwiftUI is declarative, and is very easy to pick up. Make use of the Preview canvas so you can see changes you make without having to build and run your code. Happy coding!

How about incorporating a well-designed iMessage Sticker pack? Someone in a top hat saying "Rapscallion!" - that sort of thing? You need to add more functionality. An app that just plays a bit of audio is not really of any use.

Yeah, I'd say that's minimal functionality, and I'm not surprised it got rejected. The App Store is full of apps that don't do much. Apps need to do a lot more than that. Why not include a write-up about each word, maybe showing its history etc.? How about showing the differences between different languages? And similarities - what's the closest American word to poppycock? What's the closest Irish word to codswallop? Right now, your app has very little functionality, but before you go ahead and add more, decide whether what you think about adding is of any use. Will developing the extra functionality make it more likely to get accepted, or will you be wasting your time?

Where does it crash? Honestly, you have to help us out here. Have you narrowed it down to a specific character in your string? Is it in the attributed text? Where?!

Well, you haven't given us any information on what your app does so our answer right now will likely be: "Put more functionality in it". What does it do at the moment? What do you think you could add to it? If it's just a wrapper around a website then don't bother going any further.

Which application? You should get in touch with the specific developer of an app if you want to test their app in TestFlight, not fire-hosing everyone on these forums.

Okay, according to this forums issue "That is the expected behavior. In the sandbox, you can fetch in-app purchase information in the Simulator. However, you cannot purchase them. To test purchasing in-app purchases in the sandbox, run your app on a device." None of the Apple Developer Documentation pages explicitly point this out. Also, heaven forfend you supply a reasonable error message that might give us a clue as to the actual problem! Telling us about "password reuse" is about as far away from "can't do this in the Simulator" as you can get. I'm raising an FB (FB16366964) on this so that others don't waste days trying to figure out where they're going wrong.

No one else is experiencing this? I'm the only one developing an in-app purchase who's getting this error?

Provide some code. Without it, we can't really tell whether there's a bug or you've done something wrong.