We have been developing a new app for scanning documents and photos for six months. This app has many unique features that other apps don't have. The app automatically detects holes on the documents that have been punched with a hole punch and removes them from the document. The corners of the detected document are automatically moved inwards to get clean edges, the user can set how many pixels to indented. This app recognises the text very accurately and inserts it into the PDF document behind the image at the exact position and text size as the text on the image. The PDF generated by the app can be searched for text and the text can be marked and copied. Another important feature that no other app in the App Store offers is the function that all four corners of the document are shown enlarged in four circles and are visible at the same time. The user can see immediately if the corners have been recognized satisfactorily or if they should be corrected. The user can move the corners either on the document or directly in the circles. This feature is very suitable for users with visual impairment and makes it easier to use for disabled people. We also put a lot of work into the very small file size of the generated PDF. The quality improvement of the documents is very good. We filter away almost all noise, disturbances and dirt spots and improve the appearance of the text enormously. In addition, we translated the app, the app description and the keywords into 33 languages. We created and uploaded 1320 screenshots with a lot of effort. (33 languages x 10 screenshots x 4 devices) Our two daughters (10 and 12 years old) worked on the app for the first time in their lives. They helped us with the design, tested the app, took some screenshots, contributed ideas for the description for the store. Happy to finally finish the app after long months, we submitted it for review. The next day the rejection: Guideline 4.3 - Design We were shocked. We have 19 apps in the App Store for many years. One of these apps has a similar design to the new app in some views. But the functionality of the two apps is completely different. These apps are impossible to combine into one. And why should we reinvent the design of every app from scratch when it works very well and looks good? The requests for the exact reason for the rejection in the app review page are not answered. The same rejection text is written back every time. We have submitted an appeal but have not received a response yet. We are now worried and uncertain. We had other new app projects planned, but it's too dangerous to invest money and hard work for months and then find out that the app is being rejected. A large part of our income comes from revenue from the App Store. Our apps have millions of active users. Now we are really thinking about whether we should urgently focus on a business in a completely different area. After all, we have two children counting on us. The exact text of the rejection: Guideline 4.3 - Design We noticed that your app provides the same feature set as other apps submitted to the App Store; it simply varies in content or language, which is considered a form of spam. The next submission of this app may require a longer review time. Next Steps Review the Design section of the App Store Review Guidelines. Ensure your app is compliant with all sections of the App Store Review Guidelines and the Terms & Conditions of the Apple Developer Program. Once your app is fully compliant, resubmit your app for review. When creating multiple apps where content is the only varying element, you should offer a single app to deliver differing content to customers. If you would like to offer this content for purchase, it would be appropriate to use the in-app purchase API. Alternatively, you may consider creating a web app, which looks and behaves similar to a native app when the customer adds it to their Home screen. Refer to the Configuring Web Applications section of the Safari Web Content Guide for more information. Submitting apps designed to mislead or harm customers or evade the review process may result in the termination of your Apple Developer Program account. Review the Terms & Conditions of the Apple Developer Program to learn more about our policies regarding termination.

Our workaround is to do all storyboard work with XCode 13.4.1. There are no problems with that version. Of course, it's not a long-term solution.

It looks like it has been fixed again in iOS version 15.7.3. So far we haven't had any crashes reported with this new version.

I also tried setting NSHighResolutionCapable to false in the Info.plist for Xcode. Xcode then starts in the simple resolution, but the values are still randomly changed by the Interface Builder when I change something in the storyboard.

I still have this problem. Unfortunately I haven't found a solution. In all projects, values are changed randomly from the Interface Builder when I change something in the storyboard. I still do not know why. I thought it might be the resolution of the connected monitor, because of the scaling. But it also happens with the MacBook only, without a second monitor connected. After I change something in the storyboard, I always have to manually synchronize the files with a text comparison program to undo the unwanted changes. I could of course program the whole design in source code. Unfortunately, that is a lot of work. The apps have been working for years with the design in Interface Builder and only small adjustments are made in the source code when the device is rotated, for example. I don't want to move everything to the source code now. It would be nice to find the cause and fix it so everything can be done reliably in Interface Builder again. Unfortunately, I marked this topic as solved too early. The accepted answer isn't the solution to the problem, but I can't change that now.

Installing the new operating system was not the reason why it suddenly worked properly. The solution was to set the zoom in Interface Builder to 100% before changing anything on the storyboard.

Yesterday I updated the operating system of my MacBook to macOS Ventura 13.0 and the problem described above in the Xcode Interface Builder is gone. It works perfectly again on the new operating system. Now only those values are changed that I actually change myself.

Do the developers have to take care of this crash themselves or will there be an iOS 15.7.1 version in which this issue is fixed?

An important line of code was missing. After I added this line, everything is displayed correctly with iOS 16 as well. [self addChildViewController:secondViewController];

Unfortunately, the two buttons of UIBarButtonItem are also placed incorrectly in the empty test project under iOS 16 if I do everything as in the real project. I add the view of a second UIViewController to the main view and then create the UINavigationBar on top of the second UIViewController's view. It worked fine until iOS 15.5. Unfortunately not with iOS 16. Does anyone know how I can fix the problem? UIEdgeInsets safeAreaInsets = self.view.superview.safeAreaInsets; secondViewController.view.frame = CGRectMake(safeAreaInsets.left, safeAreaInsets.top, self.view.frame.size.width - safeAreaInsets.left - safeAreaInsets.right, self.view.frame.size.height - safeAreaInsets.top - safeAreaInsets.bottom); secondViewController.view.backgroundColor = [UIColor darkGrayColor]; [self.view addSubview:secondViewController.view]; UINavigationBar *navigationBar = [[UINavigationBar alloc] initWithFrame:CGRectMake(0, 0, secondViewController.view.frame.size.width, 44)]; [secondViewController.view addSubview:navigationBar]; UINavigationItem *navigationItem = [[UINavigationItem alloc] init]; navigationItem.leftBarButtonItem = [[UIBarButtonItem alloc] initWithBarButtonSystemItem:UIBarButtonSystemItemCancel target:self action:nil]; navigationItem.rightBarButtonItem = [[UIBarButtonItem alloc] initWithBarButtonSystemItem:UIBarButtonSystemItemDone target:self action:nil]; [navigationBar pushNavigationItem:navigationItem animated:NO]; With the code below it looks good even with iOS 16, but I really need the first method as in the code above. UIEdgeInsets safeAreaInsets = self.view.superview.safeAreaInsets; secondViewController.view.backgroundColor = [UIColor whiteColor]; UINavigationBar *navigationBar = [[UINavigationBar alloc] initWithFrame:CGRectMake(0, safeAreaInsets.top, secondViewController.view.frame.size.width, 44)]; [secondViewController.view addSubview:navigationBar]; UINavigationItem *navigationItem = [[UINavigationItem alloc] init]; navigationItem.leftBarButtonItem = [[UIBarButtonItem alloc] initWithBarButtonSystemItem:UIBarButtonSystemItemCancel target:self action:nil]; navigationItem.rightBarButtonItem = [[UIBarButtonItem alloc] initWithBarButtonSystemItem:UIBarButtonSystemItemDone target:self action:nil]; [navigationBar pushNavigationItem:navigationItem animated:NO]; secondViewController.modalPresentationStyle = UIModalPresentationFullScreen; [self presentViewController:secondViewController animated:NO completion:nil];

I have now made an empty test project where I do nothing else than add the two UIBarButtonItems to the UINavigationBar in the source code and it is displayed correctly under iOS 16. So the problem is not with the iOS 16 but with my source code in a specific project. It's just weird that it shows up correctly on iOS 15.5. Unfortunately I haven't found the cause of the wrong placement of the buttons in my project yet.

We also have this problem (PHPhotosErrorDomain error 3300) with all our apps since iOS 15. Before that, the pictures were saved in the album for years without any problems. This only happens on some of my users' devices. We could not reproduce the problem on our test devices. Unfortunately, we can't fix this issue.

We also have this problem with all our apps since iOS 15. Before that, the pictures were saved in the album for years without any problems. This only happens on some of my users' devices. We could not reproduce the problem on our test devices. Unfortunately, we can't fix this issue.

The second Apple employee was able to help me via email. I was able to agree to the agreement and update the app. It took two days with the email support. In the time of the holidays it is a good response time in my opinion. Thanks to the Apple team for the quick help.

The second Apple employee was able to help me via email. I was able to agree to the agreement and update the app. It took two days with the email support. In the time of the holidays it is a good response time in my opinion. Thanks to the Apple team for the quick help.