Thats all it shows
I'm not sure whats wrong has it doesn't tell me.
it shows its linked to the language
Solution: I had the same problem. With the new update, there is a Media Manager beneath the screen shots. Even though it is giving you a Language error, the problem is with the screen shots. Simply open the media manager and make sure that every size either has its own image or you can click the checkbox to use the two required sizes. That fixed my Language error issue.
I met the similiar situation yesterday, I thought that's result from the iTunes connect update August 8 2016, red exclamation by all localized language without others information. If you meet this situation from August 8 2016, maybe it's the case.
I contacted Apple support and finally submitted new version since I filled up screen-shots for all sizes.
while you can upload the maximum size screenshot and 're-use' it for smaller size at 'Media Manager' page.
When I update the version of my App, also encountered the same situation. After trying various methods, the solution is found.
upload a screenshot of the non-primary language,
change the primary language,
modify the non-primary language screenshot,
change back the primary language.
Yeah Succeed!!!
When you choose screenshots, don't use 5.5 inch one for 3.5 screens.
Make sure this is unchecked.
It will work after you uncheck it.
Try the following:
Click on Pricing tab and choose Price Tier as Free or <your_price>
Otherwise check Rating if it is set properly.
Eventually check if you selected some extra languages to localize (even if I don't think so looking at your images)
Related
This is a very noobie question, but I can't seem to find any specifics on it from searches.
For my iOS app, do I manually increase the version and build numbers myself from the "General" tab in xcode, or is it done through the code signing or what?
Updating it myself seems simple, but I feel like maybe thats not what I'm supposed to be doing.
Thanks
You assign manually from Xcode itself and even if you want it automatically then also it is possible
This numbers are just for unique identification on app store, so every time you need to change the version number from previous one
You can go through this link
https://developer.apple.com/library/ios/technotes/tn2420/_index.html
For automatic increment use agvtool
visit https://developer.apple.com/library/ios/qa/qa1827/_index.html
I submitted my TestFlight build, and not I'm trying to select it for external testing. I've done this with the prior beta version, and with several other apps.
The problem is I can't click the Next button. All the fields are clearly populated. Also of note, when this happened yesterday there were Support and Marketing fields. Today (for English) they are not there.
Anyone else ever experience this?
Hello my dear friend there,
I am also having your issue this morning. After several trials and errors, I found that turn out the next button greyed out just because we have to fill all description field needed for all languages we choose.
Pictures below will explain this:
So you have filled all of those needed descriptions. Then you have to notice that you can select language in this dropdown button
Picture above explains that I have two language localized, Indonesian and Indonesian. May be different in your version, try to change the language with another your localized language. Those descriptions that you have filled is becoming blank again! And needed to be filled again!
Fill all of those descriptions, than the next button should be clear and clickable!
So the problem is we are not familiar yet with this new Test Flight's select build screen and C'mon Apple, I thought you are the best man in earth about User Experience.
Update:
I think finally Apple realize this lack of User Experience, they added a notification to complete all required fields for each localization so that we can click next.
I ran into this issue with only one app language. Turning off the stylesheet and setting the "Have you made any significant changes to this build since your previous submission?" phrase to yes/no made the most likely broken code on that page working again - after you reenabled the stylesheet.
It's definitely Apple's fault.
CocoaPods auto-generates the Acknowledgements.plist file so that you can include that in your settings.bundle.
Following this, I have added Acknowledgements.plist into settings.bundle.
Acknowledgements.plist looks like this:
This appears nicely on iOS 8 like this (as intended):
However, iOS 9 inserts big blank spaces between title and footerText, which makes it ugly:
It looks like this is not this file (Acknowledgements) specific and iOS 9 in general puts huge vertical spaces between title and footerText. The question is, how can you solve this situation and put nicely formatted Acknowledgements in plist?
Good observation! I noticed the same some time ago, too. Hoped that this was already fixed.
Investigation
For me some footer texts are shown correctly. Those were very short, like just two lines. The longer the FooterText is, the larger is the empty space. E.g. Realm Database has a very long license text which leads to an empty space larger than one single device screen after its title and before its Footer.
I edited the Acknowledgements.plist manually to see if the line breaks make a difference: While keeping the text as long as it is I removed the line breaks.
Results
Unfortunately removing the line breaks does not help. So it's really related to the content length. Looks like it's a TableView and the row height calculation is just far off.
However, I didn't find any workaround. Title key is limited in its length so this cannot be used as a workaround. FooterText really needs to be fixed by Apple.
I filed it under rdar://24837397
There are several other bugs in the System Settings.app which are disturbing during development:
(Crash) Open the Acknowledgements section of your App. Run a new debug build of your App via Xcode and try to switch back to the Settings.app. Due to copying a new Settings.bundle with updated Acknowledgements.plist the Settings.app crashes.
(Missing content) Open Device Settings and scroll to your App's settings, but do not open them yet. Repeat the step from above and run a new debug build via Xcode. Switch back to Settings.app and try opening your App settings: Empty settings page shown, only permissions like Core Location and Mobile Data are available. You have to close Settings.app via the task switcher to see the new content of your Settings.bundle.
Beside those two bugs it drives me nuts that Settings.app doesn't have a section index. Scrolling to my own Apps during development is an unnecessary waste of time.. I know about the new search but that's also slower that an index just for the 3rd party Apps.
Edit: If you stumble upon this, please file a Radar too! This is important to really get it fixed, see https://blackpixel.com/writing/2012/02/radar-or-gtfo.html.
This is a bug in iOS 9, the problem has been fixed in iOS 10. Unfortunately nothing can be done for users that are still running iOS 9.
If you're using CocoaPods or Carthage, AckAck works well to generate the Acknowledgements plist for you. It removes unnecessary line breaks/indentation and generates a separate plist for each framework (making it less of an issue on iOS 9).
https://github.com/Building42/AckAck
(I'm the creator of AckAck)
I suspect that the answer is 'no' - but perhaps I'm missing something in the api...
I'm aware of the constant UIButtonTypes for UIButton:
http://developer.apple.com/library/ios/#DOCUMENTATION/UIKit/Reference/UIButton_Class/UIButton/UIButton.html
But I've also seen Apple use the exclamation badge within their apps, for example, the Reminders app:
Does anyone know if that button/badge is available?
Or am I making my own?
As I commented, you won't be able to use this button directly.
I don't think you can point to any source to say this, but from my own experience, I never found this button.
But, what you can do, is create or find the button's image. The second option is the easiest one ;)
I found this, giving you all iOS' images (iOS 4.3, but still good) : All stock iOS 4.3 UI Images.
Or you may use directly these normal/selected retina images (comming from the above link) :
And the non-retina versions :
Quick note, you may want to use this button very carefully. As it is a system image, you must use it the way iOS uses it. If you try to use it in an unappropriate context, your app may get rejected by Apple.
I'm building a mobile application using Flex.
I'm trying to set softKeyboardInputAreaOfInterest on each inputs to include the button underneath. The area of interest is smaller than the remaining screen space left by the soft keyboard, and I've set it on viewActivate, ensuring that the correct dimensions are passed.
However, I'm testing in iOS and it just doesn't seem to be working. The correct dimensions are being traced when I set the rect, but the panning behaviour is incorrect.
I've found one or two unanswered posts on this in other threads too. Surely this property wasn't created and documented, but not actually implemented. It seems to do absolutely nothing.
At this stage, I can't get find a way of guaranteeing that both the input field and the button at the bottom of the form are panned into view.
Please help if you can!
It's a bug – softKeyboardAreaOfInterest doesn't work on iOS. I was in contact with the Adobe AIR team during the AIR prerelease in July. They confirmed the bug and added a sentence to the online AS3 docs ("This property is not available on iOS").
I just tested it again today with the newest version of AIR (version 3.5.0.600) and it's still not working on iOS, but the online AS3 docs have removed the sentence about softKeyboardAreaOfInterest not working on iOS. I'm guessing this is an oversight.
Update, Nov 19 '12: For AIR 3.5, the removal of "not available on iOS" in the AS3 docs turned out to be an oversight which has been corrected. This property still doesn't work on iOS with AIR 3.5.
Update, Nov 20 '12: And today's word from Adobe is that it's not a bug, softKeyboardAreaOfInterest is just not enabled on iOS.