I agree with @Claude31. You should put all the functionality in one app that can be used on an iPhone or iPad, then - with your two devices - allow the user to designate one of them as the Camera and the other as the Controller. Note that the app should work on both iPad and iPhone, so you may have to change the layout of the iPad app you've already created.

Are your project files on your iCloud Drive? Are you opening the projects from there? I use iCloud Drive to store my files, and it will occasionally delete some of them inside folders, including inside package files. I raised a feedback report for this at least a year ago. It doesn't affect just Xcode stuff, so important folders of files I now zip up as well. I'd ask you to raise an FB, too.

Same with any job in tech. Software testers have to learn Selenium, Webdriver, Cypress, Playwright, Postman, security testing, functional testing, load/stress testing, performance testing, UI testing, API testing... And when someone finally creates some sort of 'AI'-powered test tool that actually works and doesn't just cause issues, they'll have to learn that, too.

I think that's expected behaviour. As you've said, it applies the modifier to each item in the Group. With .onAppear it wouldn't make sense to do the same thing three times. All three Text views appeared, why would you want to call a method three times, or change a variable three times? For .toolbar you're adding three Buttons, and I would say that's what you would want to happen, no? Three buttons with the same format, style, etc.

You can edit your post within an hour of posting it. If you're outside that window, just add a reply to the original post. Don't create duplicate posts.

Okay, thanks for that. What are you expecting us to do with this? Are you a developer and you're finding that something isn't working? If so, is there some code?

That's a security alert that gives the user the opportunity to confirm or deny access for your app to devices on their local network. Bypassing that alert would be a massive no-no. (If an app could bypass it, what's the point in the alert...?) You need to handle the situation where the user confirms access, and when they deny access. When they deny, you should give them reasons as to why it's required, and give them instructions on how to grant access.

A few things here: These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. This is not the place for product support. Finally, you knew this MacBook was stolen, and I'm not about to help you in any way. That MacBook belongs to someone else. You have received stolen goods. You will not get any help from us here.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. It might be intentional, but I don't know. Perhaps it's to stop people deleting too many things at once. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

If you could maybe show us your code we might be able to see whether you're doing something wrong, or are missing something.

They won't, but I have an electric Wi-Fi radiator at home but the app for that got through the review process. What you need to do is ensure the app is functional, i.e. make sure it doesn't just crash because the Raspberry Pi device isn't present.

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums. You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

You can edit posts within an hour. Marking this as a duplicate.

I've figured it out. I was using a global context variable, but it seems to work only if I create a new variable every time I want to use the policy. Doesn't make sense to me, but this doesn't work: let context = LAContext() func authenticate() { context.evaluatePolicy... } While this does: func authenticate() { let context = LAContext() // <-- Moved inside the function context.evaluatePolicy... }

Found this on the web: In the Finder, click the Go menu and choose Go to Folder. You now need to navigate to several different locations, look for files with Grammarly in their name, and drag them to the Trash. Here are the locations you need to check: ~/Library/Application Support/ ~/Library/Caches/ ~/Library/Saved Application State/ Note that ~ means your user folder. If you also have the browser extension: Open Safari, then click the Safari menu and select Settings. Switch to the Extensions tab. Select Grammarly for Safari and click the Uninstall button. Confirm to remove it.