Search results for

4.3

572 results found

Post

Replies

Boosts

Views

Activity

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 Guideline 4.3 -- made from template... but they are not.
If you are talking about FastFinga 3, I already got approved from Hasegawa san from Apple Review Board. He clearly said that Handwriting Keyboard is not similar to FastFinga 3 because Handwriting Keyboard is a keyboard extension, although he ordered me to remove FastFinga version 2 because keeping multiple versions is against Guideline 4.3 and not allowed on App Store.Even he said that I still doubt Handwriting Keyboard was rejected because of FastFinga 3. I think the review team is very confused and not operating well. FastFinga is more like a drawing app. Handwriting Keyboard is a keyboard extension, which contains handwriting recognition engine. It is like Apple's built-in Simplified Chinese Handwriting Keyboard.
May ’18
Guideline 4.3 - Design wrong rejections
Earlier I had about 20 similar travel apps. All of them received a rejection for the reason of Guideline 4.3 - Design Spam. Later, according to Apple recommendations, I have combined all similar apps into the one container app.Now, when I try to publish any new apps or updates I get the same rejection (Guideline 4.3 - Design). It looks like an automatic rejection for everything that I try to upload. I have to constantly ask for a re-check. After the moderator team re-checks the app, the app is passed successfully without any rejection.Last time I tried to publish stickers app. This app is based on a Sticker Pack App template in Xcode and has unique and exclusive stickers for iMessage. And this app gets the same rejection. I'm sure that after my request this stickers app will pass successfully. But I do not understand why I have to ask for a re-check every time.New apps and updates still get wrong rejection after I fixed everything that Apple requested (combined all similar apps into the one
8
0
4.8k
May ’18
Reply to Guideline 4.3 -- made from template... but they are not.
Here is the list of our apps that got Guideline 4.3 rejection so far...• https://itunes.apple.com/app/id926102392?ls=1&mt=8 (approved after one month)• https://itunes.apple.com/app/id1272669652?ls=1&mt=8 (approved after giving up the obsolete version and IP commentary book reader (id1217317638))• https://itunes.apple.com/app/id978926628?ls=1&mt=8 (no new update is allowed)• https://itunes.apple.com/app/id325361059?ls=1&mt=8 (no new update is allowed)• https://itunes.apple.com/app/id560440657?ls=1&mt=8 (approved after several phone calls)• https://itunes.apple.com/app/id1020070997?ls=1&mt=8 (no new update is allowed)• https://itunes.apple.com/app/id1217317638?ls=1&mt=8 (no new update is allowed)• https://app-liv.jp/320090110/(told to remove on the phone because it violates Guideline 4.3)
May ’18
Reply to Rejected - Guideline 4.2 - Minimal functionality
You've seen it and App Review has seen it, so we're left to our imagination what they witnessed that prompted your exact rejection, but I'd speculate that a tilt-puzzle is hardly original/unique these days. MazeTilt, HydroTilt, Tilt-to-Live, FallDown, Tilt Tilt Ladybug, Block tilt Escape, Gate Tilt, tilt The Box, Time Tilt Ball....on and on, the store seems well saturated, since at least 2010. Maybe they've just had enough...surprised they didn't just flag it w/4.3.
Jun ’18
No crypto user for encrypted APFS volume!
After an update to High Sierra, I'm trying to unlock my volume (disk1s1) but cannot anymore. This is the info from terminal:APFS Container (1 found) | +-- Container disk1 C8022E32-744D-414E-9246-29ADDB0357F3 ==================================================== APFS Container Reference: disk1 Size (Capacity Ceiling): 500068036608 B (500.1 GB) Minimum Size: 500068036608 B (500.1 GB) Capacity In Use By Volumes: 485282820096 B (485.3 GB) (97.0% used) Capacity Not Allocated: 14785216512 B (14.8 GB) (3.0% free) | +-< Physical Store disk0s2 438AD64B-835E-418D-B0DF-32A3A0B7500A | ----------------------------------------------------------- | APFS Physical Store Disk: disk0s2 | Size: 500068036608 B (500.1 GB) | +-> Volume disk1s1 6C587DE6-9C8D-3792-9144-34FBE59AE9F6 | --------------------------------------------------- | APFS Volume Disk (Role): disk1s1 (No specific role) | Name: Macintosh HD (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 382597644288 B (382.6 GB) | FileVault: Yes (Locked) | +
1
0
8.8k
Jun ’18
About Guideline 4.2.6
In Guideline 4.2.6.Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences.This Guideline is very similar to Guideline 4.3.How to comply with Guideline 4.2.6 without violating Guideline 4.3?Is it possible to just use the tool to create an similar app and submit it using the client's developer account?Is there an impact if the customer's developer account is an individual developer account and not an enterprise developer account?
0
0
1k
Jun ’18
Request Authorization at Launch Time not triggering request authorisation popup
Since a recent upgrade - Xcode 9.4, WatchOS 4.3, iOS 11.4, the Request Authorization at Launch Time in my watchApp is no longer generating the request authorization pop-up on the phone.My requests are appearing as if the user had provided authorization.Yes, I have uninstalled the app and rebooted all devices many times to see if there was something left hanging around.In itself, that's not a problem, as I want my users to accept Notifications, they are intrinsic to my app, but the problem is that the Simulator is not requesting authorization and denying it incenter.requestAuthorization(options: [.alert, .sound]) { (granted, error) in print(granted: (granted), error: (error!)) } }
2
0
1.2k
Jun ’18
4.3 Design: Spam Rejected. Please help me resolve this.
Hi everyone.First sorry for bad EnglishOur app have been rejected. I asked the specific solution but they sent me message belowWe do have an app/game have same feature but we removed it already.Please suggest me how to resolve this issue. Are we need to permanent delete it (how to do it?), or update the old app?From Apple4. 3 Design: SpamHello,We are not able to provide feedback on app concepts or features, but we recommend evaluating your suggestions against the App Store Review Guidelines, as well as the iOS Developer Program License Agreement (PLA), and the iOS Human Interface Guidelines.Additionally, if you are considering implementing any of the following functionality, we recommend reviewing all associated reference material and other resources available on Apple Developer for any additional requirements.- Apple Developer- Apple Copyright and Trademark Guidelines- Game Center- iCloud- In-App PurchaseYou may also choose to post a question in the Apple Developer Forums.Best regards,
0
0
1.5k
Jun ’18
Reply to Solution to template apps?
Search this forum for '4.3 spam rejection'. Apple wants you to generate a single app that can be directed by the user to a specific 'client' or 'ball team' or 'barber shop' rather than one for each client, ball team or barber shop in every town in America. Another solution may be to have each of your clients create their own developer account and submit the app under that account.4.3 Spam Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase.......
Aug ’18