Search results for

“4.3”

797 results found

Post

Replies

Boosts

Views

Activity

Reply to 4.3 Design Guidelines - Apple please reconsider how this is enforced.
I have loyal users of many years. Not many, but they have supported Apple's products for many years.Apple just keep on damaging user experience by rejecting the updates because of guideline 4.3.I have to explain to users that I can't update our productivity apps because Apple just don't allow updates even though the updates are ready to be released only if Apple allow to do so.The apps are keeps on crashing on users' phone and users are unable to access their data accumulated on their phone for several years. I don't understand why Apple keep on damaging tthier reputation by donig this.I am not being harrassed by Apple, but users are.
May ’18
Reply to Guideline 4.3 -- made from template... but they are not.
I got another Guideline 4.3 rejeciton today.This time it is a keyboard extension that enables Japanese and English handwriting (handwriting recogniton) system wide.View on App StoreI immediately appealed to the review board, but even the appeal was rejected just in an hour. They said they gave us all the reasons (yes, made from a template as usual) and my request for detailed explanation was denied.-----We got a phone call on June 6. Finally they decided that the app is unique enough to be appoved. It took several weeks to get attention from the review board this time again. The resolution centre was purly waste of time. It did not resolve anything.
May ’18
Reply to Visual Novel Game Rejection due to Design 4.3 (a) Spam
To add to this case, and for better understanding of the issue, we've noticed that there's not been any activity on our servers during the second review of the game. The evaluation seems to have been taken without actually evaluating the in-game changes we've made. We did find server activity during the first review. The game had a dating simulation feature (think of profile swiping between fictional characters to unlock storylines), and we assumed that having a “dating resemblance was not in accordance to the 4.3 design guidelines (the one that explains developers should refrain from piling up on already saturated categories, such as dating). Hope this makes things a bit clearer. Thanks again for any insight or feedback on how to get things right.
Oct ’24
Reply to App rejected for Guideline 4.3(a) due to similar app on old account I cannot access
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Jun ’25
Reply to Dealing with Guideline 4.3(a) on a Legitimate B2B Legacy App Migration (Unable to redesign)
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Jun ’26
Reply to 4.3a
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Apr ’26
Reply to Rejected for Guideline 4.3(a) - Spam, looking for advice on next steps
I got the same body on twelve updates in one batch two nights ago, so I have my own measurements rather than an answer from Apple. Two things narrowed it down faster than anything else I tried. First, read the body rather than the number. Apple's published text for 4.3(a) is about multiple Bundle IDs of the same app — the a separate map app for every city example. The sentence you quoted, about a similar binary, metadata and/or concept as apps already on the store, is the substance of 4.3(b). Those point at two different things: 4.3(a) is a question about your own catalogue, 4.3(b) is a question about how your app reads next to what is already there. I would not raise that as a gotcha, but it does tell you which side to go and measure. Second, measure your own side before you ask anything. It is cheap and it shrinks the surface fast: Byte-compare every source file against every other app you ship. shasum every file, then look for collisions. I expected to find shared files
Aug ’26
Reply to Words can’t truly explain this.
Finally someone asking; 1st Submission on June 8th Rejection 1: June 11th - A subtle yet valid UX issue, fixed that day itself and resubmitted. Rejection 2: June 12th - 1st Guidelines 4.3(b) rejection. The app is nuanced, so there were 2 accounts attached in the reviewer note with concisely explained details so they understand the nuance while reviewing the app as a whole. The reviewer only logged into one account and rejected. I resubmitted the same day clarifying this and that they needed to login to the other account to fully understand. Rejection 3: June 24th - Guidelines 4.3(b) rejection again. The reviewer only logged into one account again and rejected it. At this point I heard about App Review Board and I thought that might be the way to do this because I clearly explained why previously but the reviewer still rejected. So I made a App Review Board appeal. 3 weeks passes by no response, that's when I made my initial forum post asking how long does this process take. At the same time,
Aug ’26
Reply to arrays
This function you have is set up to receive an array of Doubles and let you refer to them as costa: func myfunc(costa: [Double]) { // some code } If you're calling the function like this: myfunc(costa: []) then you're passing in an empty array. [] means an empty array. If you want to pass in some values, you need them in the array, e.g.: myfunc(costa: [1.0, 2.1, 3.2, 4.3]) If you need to return an array of Doubles - or anything - you would use a function like this: func myfunc(costa: [Double]) -> [Double] { // some code return myArray // which would be an array of Doubles } A very useful feature of Swift is the ability to hide the name of the variable, so you don't have to enter it every time. Just put an underscore before the first variable name in the function's signature, i.e.: func myfunc(_ costa: [Double]) { // some code } This lets you access the array of Doubles in costa. To call it you would use: myfunc([1.0, 2.1, 3.2, 4.3]) A similar helpful feature is replacing the underscore wi
Dec ’24
Reply to App rejected under 4.3(a) Spam: original app, single-app account, appeal filed, no response
I think the key is the thing you already noticed: the reviewer probably never saw what makes the app unique. On an iPad with no climbing video in Photos and no Apple Watch heart-rate data in HealthKit, the first screen is New project and Live capture. That looks like a generic camera app, and 4.3(a) is judged largely on that first impression and the metadata. What I'd change before resubmitting, rather than waiting on the appeal: Add a built-in sample project: a short bundled climbing clip with sample heart-rate data, opened from something like Try a sample climb on the home screen. Then the overlay and zoom-and-follow work instantly, without Photos, HealthKit data or a Watch. Put it at the top of the review notes: The core features need an Apple Watch heart-rate recording and a climbing video. To see them without either, tap Try a sample climb on the home screen. Check how heart rate is positioned in your name, subtitle, keywords and screenshots. Heart rate is one of the most crowded categories and
2w
Reply to Crashplan 4.3 Partically Operational/Broken
Max108, First, thanks for link. Tired it via another forum post, and same result. Believe it has to do with Crashplan reliance on Java. It has it's own Java built into the application. The strange thing as shared, is the backups are still working from the taskbar/notification tray. However, when launch the UI to try to set configurations, modifiy UI settings, etc. it freezes and you cannot select anything at all. The UI is completely unresponseive. I'm interested to see what Apple/Crashplan have to say. As shared, submitted incidents with both for futher investigation. I'm surprised Crashplan wasn't doing some preliminary testing with Crashplan 4.3 and DP1 of El Capitan seems to me someone might have dropped the ball. We'll see.
Topic: App & System Services SubTopic: Core OS Tags:
Jul ’15
Reply to 4.3 Design Guidelines - Apple please reconsider how this is enforced.
Guys, if you have enough resources there's still another way: you could create separate account for each of your apps (would work fine for white label and similar business models). As i have said above, I've tried that way and also got 4.3 rejection, so our aim now is to figure out how apple's review algorithms find identical or similar apps and how we could pass through it. We should find a way to confuse/obfuscate code and app's structure, so the bot can't identify copies.If there's no fair review, we should find our own way to make it fair. I understand that this method would help those who just spam on AppStore, but at least that'll attract apple's attention to our problem and problem in its algorithm
Nov ’17
Reply to Apple Developer Program account under investigation
I have a 6 million downloaded basketball game, I made a soccer game based on it by 1.5 years. Apple rejected the soccer game and told me that they will terminate my account after 14 days, I feel inexplicable, I have never sell this game, I transferred the basketball game to a new account because I don't want to lose it after 14 days.I submited the soccer game again for review by another new account.But it was rejected by 4.3 spam, ridiculously he said that I copied my own game, because I used to submitted the game by the terminated account. After that the new account under investigation.I did't update the basketball game for 6 months,I am afraid the account under investigation if I update it.
Oct ’19
Reply to App Store Guideline 4.3(b): A Barrier to Meaningful Innovation?
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple Experts event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Apr ’26
Reply to 4.3 Design Guidelines - Apple please reconsider how this is enforced.
I have loyal users of many years. Not many, but they have supported Apple's products for many years.Apple just keep on damaging user experience by rejecting the updates because of guideline 4.3.I have to explain to users that I can't update our productivity apps because Apple just don't allow updates even though the updates are ready to be released only if Apple allow to do so.The apps are keeps on crashing on users' phone and users are unable to access their data accumulated on their phone for several years. I don't understand why Apple keep on damaging tthier reputation by donig this.I am not being harrassed by Apple, but users are.
Replies
Boosts
Views
Activity
May ’18
Reply to Guideline 4.3 -- made from template... but they are not.
I got another Guideline 4.3 rejeciton today.This time it is a keyboard extension that enables Japanese and English handwriting (handwriting recogniton) system wide.View on App StoreI immediately appealed to the review board, but even the appeal was rejected just in an hour. They said they gave us all the reasons (yes, made from a template as usual) and my request for detailed explanation was denied.-----We got a phone call on June 6. Finally they decided that the app is unique enough to be appoved. It took several weeks to get attention from the review board this time again. The resolution centre was purly waste of time. It did not resolve anything.
Replies
Boosts
Views
Activity
May ’18
Reply to Visual Novel Game Rejection due to Design 4.3 (a) Spam
To add to this case, and for better understanding of the issue, we've noticed that there's not been any activity on our servers during the second review of the game. The evaluation seems to have been taken without actually evaluating the in-game changes we've made. We did find server activity during the first review. The game had a dating simulation feature (think of profile swiping between fictional characters to unlock storylines), and we assumed that having a “dating resemblance was not in accordance to the 4.3 design guidelines (the one that explains developers should refrain from piling up on already saturated categories, such as dating). Hope this makes things a bit clearer. Thanks again for any insight or feedback on how to get things right.
Replies
Boosts
Views
Activity
Oct ’24
Reply to App rejected for Guideline 4.3(a) due to similar app on old account I cannot access
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Replies
Boosts
Views
Activity
Jun ’25
Reply to Dealing with Guideline 4.3(a) on a Legitimate B2B Legacy App Migration (Unable to redesign)
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Replies
Boosts
Views
Activity
Jun ’26
Reply to 4.3a
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Replies
Boosts
Views
Activity
Apr ’26
Reply to Rejected for Guideline 4.3(a) - Spam, looking for advice on next steps
I got the same body on twelve updates in one batch two nights ago, so I have my own measurements rather than an answer from Apple. Two things narrowed it down faster than anything else I tried. First, read the body rather than the number. Apple's published text for 4.3(a) is about multiple Bundle IDs of the same app — the a separate map app for every city example. The sentence you quoted, about a similar binary, metadata and/or concept as apps already on the store, is the substance of 4.3(b). Those point at two different things: 4.3(a) is a question about your own catalogue, 4.3(b) is a question about how your app reads next to what is already there. I would not raise that as a gotcha, but it does tell you which side to go and measure. Second, measure your own side before you ask anything. It is cheap and it shrinks the surface fast: Byte-compare every source file against every other app you ship. shasum every file, then look for collisions. I expected to find shared files
Replies
Boosts
Views
Activity
Aug ’26
Reply to Words can’t truly explain this.
Finally someone asking; 1st Submission on June 8th Rejection 1: June 11th - A subtle yet valid UX issue, fixed that day itself and resubmitted. Rejection 2: June 12th - 1st Guidelines 4.3(b) rejection. The app is nuanced, so there were 2 accounts attached in the reviewer note with concisely explained details so they understand the nuance while reviewing the app as a whole. The reviewer only logged into one account and rejected. I resubmitted the same day clarifying this and that they needed to login to the other account to fully understand. Rejection 3: June 24th - Guidelines 4.3(b) rejection again. The reviewer only logged into one account again and rejected it. At this point I heard about App Review Board and I thought that might be the way to do this because I clearly explained why previously but the reviewer still rejected. So I made a App Review Board appeal. 3 weeks passes by no response, that's when I made my initial forum post asking how long does this process take. At the same time,
Replies
Boosts
Views
Activity
Aug ’26
Reply to arrays
This function you have is set up to receive an array of Doubles and let you refer to them as costa: func myfunc(costa: [Double]) { // some code } If you're calling the function like this: myfunc(costa: []) then you're passing in an empty array. [] means an empty array. If you want to pass in some values, you need them in the array, e.g.: myfunc(costa: [1.0, 2.1, 3.2, 4.3]) If you need to return an array of Doubles - or anything - you would use a function like this: func myfunc(costa: [Double]) -> [Double] { // some code return myArray // which would be an array of Doubles } A very useful feature of Swift is the ability to hide the name of the variable, so you don't have to enter it every time. Just put an underscore before the first variable name in the function's signature, i.e.: func myfunc(_ costa: [Double]) { // some code } This lets you access the array of Doubles in costa. To call it you would use: myfunc([1.0, 2.1, 3.2, 4.3]) A similar helpful feature is replacing the underscore wi
Replies
Boosts
Views
Activity
Dec ’24
Reply to App rejected under 4.3(a) Spam: original app, single-app account, appeal filed, no response
I think the key is the thing you already noticed: the reviewer probably never saw what makes the app unique. On an iPad with no climbing video in Photos and no Apple Watch heart-rate data in HealthKit, the first screen is New project and Live capture. That looks like a generic camera app, and 4.3(a) is judged largely on that first impression and the metadata. What I'd change before resubmitting, rather than waiting on the appeal: Add a built-in sample project: a short bundled climbing clip with sample heart-rate data, opened from something like Try a sample climb on the home screen. Then the overlay and zoom-and-follow work instantly, without Photos, HealthKit data or a Watch. Put it at the top of the review notes: The core features need an Apple Watch heart-rate recording and a climbing video. To see them without either, tap Try a sample climb on the home screen. Check how heart rate is positioned in your name, subtitle, keywords and screenshots. Heart rate is one of the most crowded categories and
Replies
Boosts
Views
Activity
2w
Reply to Crashplan 4.3 Partically Operational/Broken
Max108, First, thanks for link. Tired it via another forum post, and same result. Believe it has to do with Crashplan reliance on Java. It has it's own Java built into the application. The strange thing as shared, is the backups are still working from the taskbar/notification tray. However, when launch the UI to try to set configurations, modifiy UI settings, etc. it freezes and you cannot select anything at all. The UI is completely unresponseive. I'm interested to see what Apple/Crashplan have to say. As shared, submitted incidents with both for futher investigation. I'm surprised Crashplan wasn't doing some preliminary testing with Crashplan 4.3 and DP1 of El Capitan seems to me someone might have dropped the ball. We'll see.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jul ’15
Reply to 4.3 Design Guidelines - Apple please reconsider how this is enforced.
Guys, if you have enough resources there's still another way: you could create separate account for each of your apps (would work fine for white label and similar business models). As i have said above, I've tried that way and also got 4.3 rejection, so our aim now is to figure out how apple's review algorithms find identical or similar apps and how we could pass through it. We should find a way to confuse/obfuscate code and app's structure, so the bot can't identify copies.If there's no fair review, we should find our own way to make it fair. I understand that this method would help those who just spam on AppStore, but at least that'll attract apple's attention to our problem and problem in its algorithm
Replies
Boosts
Views
Activity
Nov ’17
Reply to Apple Developer Program account under investigation
I have a 6 million downloaded basketball game, I made a soccer game based on it by 1.5 years. Apple rejected the soccer game and told me that they will terminate my account after 14 days, I feel inexplicable, I have never sell this game, I transferred the basketball game to a new account because I don't want to lose it after 14 days.I submited the soccer game again for review by another new account.But it was rejected by 4.3 spam, ridiculously he said that I copied my own game, because I used to submitted the game by the terminated account. After that the new account under investigation.I did't update the basketball game for 6 months,I am afraid the account under investigation if I update it.
Replies
Boosts
Views
Activity
Oct ’19
Reply to App Store Guideline 4.3(b): A Barrier to Meaningful Innovation?
Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple Experts event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.
Replies
Boosts
Views
Activity
Apr ’26