Search results for

4.3

600 results found

Post

Replies

Boosts

Views

Activity

Register multiple developer accounts issue
Hi Apple,you forced my client to rethink it's valid white lable app solution due to the 4.3 rule (Spam restriction). Your only acceptable suggestion was to get a developer account for each of the customers for the correspondig app. The developer account forces to activate a two-factor authentication, which has to be activated on a Mac. Well it seems, that each Mac can only do it for 3 accounts, after that my client see an error, that the maxmum number of accounts is reached. My client has to migrate about 100 apps to the new accounts, how to do that without purchasing new Macs for every three accounts...?Cheers,Frustrated Developer
1
0
827
Sep ’18
setTitle for Buttons not uses complete number.
I want to set the title for a button with a double number.The problem is that the function always cuts a zero, if the last number is a 0.var number1: Double = 3.99 var number2: Double = 4.30 button.setTitle((number1), for: .normal) //Title is 3.99 button.setTitle((number2), for: .normal) // Title is 4.3 but hast to be 4.30I tried to convert it with String(number2), but the title is 4.3 too.
2
0
448
Aug ’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
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
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
Guideline 4.3 -- made from template... but they are not.
I have an app called AB Player, which is a music player that can play back user's iTunes library with speed control and A-B repeat.■ AB Player ... View on App StoreThis app was rejected becasue it violates Guideline 4.3 (Spam).I have appealed to the review board. They decided to maintaint the rejection and they told me that AB-Player app is made on the same template as many of other my apps like eLaws■ eLaws ... View on App StoreeLaws is a (sort of) law dictionary app. Users can download Japanese laws from the government website and browse locally.AB Player and eLaws are completely different apps.They are not made from a same template. They may be made from Xcode's Single view app template but that's all.I explained to them but they didn't change mind. And they didn't disclose the exact reason why they think they are made on the same template.AB Player and eLaws both use Realm Swift database frameworks and Google Mobile Ads framework, as well as UIKit, CoreText etc, but I don't think that's an issue.
23
0
9.0k
Apr ’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)
Jun ’18
4.3 guideline nightmare
As many developers have already experienced (see https://forums.developer.apple.com/thread/82935, https://forums.developer.apple.com/thread/82964, https://forums.developer.apple.com/thread/46910), Apple started to agressively apply the 4.3 guideline asking the developers to consolidate their existing apps into 1 container app. We experienced this ourselves recently.Our apps are designed to help people pass their UK theory test. As there are 5 different vehicle categories (which are not related to each other in any way) we obviously have an app for each of these categories. Apple is asking us to bundle cars, motorcycles, lorries, etc all into one container app.We already responded to the App Review team highlighting many reasons why we believe that this is a wrong application of the 4.3 guideline. Some of these are listed below:We develop all the code ourselves and we do not use any commercial templates.These apps target different sets of users (even the age profile is different)These apps co
22
0
15k
Jul ’17
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
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.
Jun ’18