I'm trying to upload new images to iTunes Connect. However, they continue to fail. I've checked many many times now and no dice. The screenshot sizes match Apple's requirements. Saving it as a .jpg continues to fail. Saving it as a .png with no Alpha continues to fail. Spent most of my work day on here finding other solutions that I've tried and still fails.
Other things I tried was using different browsers, saving the image file as generic as possible (ex. 1.png, and I've tried using screenshots pulled from an actual device as well as the Xcode simulator.
I am trying to do this via a windows machine. Has anybody been able to successfully upload screenshots through iTunes Connect using a Windows machine? At this point that is the only thing I can think of as to why it continues to fail.
Try waiting... in my experience, iTunes connect is not all that reliable, and waiting a day solved the screenshot upload issue for me.
Also, if you have not already, open the screenshots in an image editor, and insure they are exactly the right size... I have found that my screenshots always end up a pixel to skinny for some reason.
Lastly, keep in mind new rules for the iPhone 6 and 6 Plus.
Related
I wrote a parser in selenium, which clicks to different links and parses data. But from time to time I get an error
Your connection was interrupted. ERR_NETWORK_CHANGED
Perhaps this error is not related to selenium.
But, if I wait a little (about 1 second), then the connection appears again and I can continue to parse.
What way is there to solve this problem programmatically? Maybe in this case, somehow, I can reload the page until the connection appears again?
For me using a mac system and chrome for a daily basis, I encounter this problem now and then and finally found it might be helpful to solve this problem by just turning off the virtual machines or dock containers whichever can adjust your network configuration.
Maybe not fit for your case but it could be a hint. You can turn them off for a while if you have them running.
We have recently planned to switch from SQLite to Realm in macOS and iOS app due to db file corruption issue with SQLite so we first started with macOS app. All coding changes were smooth and app started working fine.
Background about app and DB usage - app really uses DB very heavily and performs too many read and writes to DB in each minute and saves big xml's to it. In each minute it writes / updates around 10-12 records (at max) with xml and reads 25-30records too. After each read it deletes data along with xml from database and my expectation is once data is deleted it should free up space and reduce file size but looks like it is growing continuously.
To test the new DB changes we kept app running app 3-4 days and DB file size went to 64.42GB and app started being slow. Please refer the attached screen shot.
To further debug, I started app with new DB file and size was 4KB but within 5min it goes to 295KB and never reduced in size even records were continuously added and deleted.
To further clarify, app uses NSThreads to perform various operations and those threads writes and reads data to DB but with proper begin\commit transactions. I also read at 'Large File Size' at https://realm.io/docs/java/latest/#faq and tried to find compactRealm but can't find it in objective c.
Can anybody please advise.
Update - I Give up on Realm
After 15days of efforts, Finally I have stopped usage of Realm and starting to fix/workaround db file corruption issue with SQLite. Realm Huge DB file issue was fixed by making changes to code for threads but then I started getting Too many open files error after running the app for 7-8 hours.
Debugged for whole week and made all possible changes and at some point looks like all was good as xcode were not showing any open files. But again I started getting Too many open files crash and then debugged with instrument and found there were so many open files to realm database, lock, commit and cv files.
I am sure there are no leaks in app and xcode also does not shows those open files in Disk usage as well. I decided to invoke lsof command in code before and after Realm calls and most of the it doesn't increase open file count but sometime n between it increases. In My app it started from 120 files to 550 in around 6 hours. Xcode looks all fine via Disk usage but instrument shows open files.
No good support from Realm team, sent email to them, just got one response. Made many changes to code following their suggestions and doesn't work at all so gave up on it. I think it's good for small apps only.
I uploaded my first iOS app today to iTunes Connect.
I uploaded it over xCode 7.2.1 and I see the app as "Processing" inside the "activity"-tab.
But under "AppStore"-tab for version 1.0 there is no app build visible. I only see the message that I should upload a build with xCode or Application Loader.
Is this normal or should I wait some time that the app is also showing up?
See the screenshots below:
Yes, this is perfectly normal. You just have to wait for it to finish processing (can take a few minutes or a few hours depending on Apple's traffic). Once it is done processing, it will appear in that builds section and you can select it as the version you want to submit. This is the same for TestFlight.
I recommend getting watchbuild and running it on your terminal so you can just get a notification on your computer when your build is done processing instead of having to keep checking App Store Connect.
It happened to me a couple of times. I just uploaded a new version (same code, just increased the version) and it was processed quite fast.
Just in case, the second time I kept the archiving dialog in the foreground.
This is normal. After uploading a build, iTunes Connect performs some processing to prepare it for TestFlight Distribution and App Store distribution.
The status of the build should go to ready after some time. Sometimes, this happens as fast as 15 minutes after uploading but can sometimes take 1 hour or longer. After the processing finishes, the build will become available to select for TestFlight betas and app submission.
Yes, this is perfectly normal. You just have to wait for it to finish processing (Can take a few minutes or a few hours depending on Apples traffic). Once it is done processing, it will appear in that builds section and you can select it as the version you want to submit. This is the same for testflight.
Additional from my personal experience (happened to me once and only once), if you submit the archive late at night on the last weekday or just before a public holiday, "sometimes" it might be processed on the next working day on the morning.
I'm at Indonesia (GMT +7), it is not uncommon for me to upload an archive around 7PM, and if it doesn't get processed in 15 minute, I usually just go home, and check it in the morning the next day. Because it happens a few time that if I upload too late, it get processed around 8AM the next morning.
I had this issue today, i tried all of the fixes suggested and found that you need to wait till the invitations are sent out. I think the servers were just very busy when i was trying to test my app.
It happened to me when I export Unity iOS build and upload it to AppStore there are more than 3 days waiting but still showing processing.
Finally, Many search things I found that Bitcode = NO here is the issue on my build I have Bitcode = YES once you change and set to NO and upload again your build it's not showing processing and it's working properly.
The best way to sum up the issue would be with a screenshot, but unfortunately my screenshots auto-save to downloads and so I can't upload them. What's happening is that when I enter the 'file select' dialog in trying to upload a file, it's automatically in the 'drive' folder and won't move to any other folder. I've tried restarting and resetting my machine, tried the upload process on a bunch of different platforms, tried using the other user account on my machine, tried updating my software, but none of these have made any difference. I can get into my downloads folder and open files from it fine outside of this context, and I can workaround by using the drag-and-drop to upload on platforms which have this feature, but otherwise I'm stuck.
I've googled extensively to see if anyone else is having this issue and have found this thread: https://productforums.google.com/forum/#!topic/chromebook-central/d7g9EEDsr8w but there's no helpful solution there (recommended a powerwash but the asker has already done this several times). I've also tried to find a solution with the help of my (programmer) employer, but no luck so he recommended asking here. It seems like it wouldn't be a hardware issue when I can still access the folder outside of this specific function, but if it were a problem with the running system it seems it would be happening across the board and therefore show up more in a google? If anyone has any suggestions I'd be very grateful as it's getting quite tiresome having to drag and drop things into Facebook messages to get them uploaded! The machine is less than a year old so if I can't find any solution I'll see about getting it replaced under warranty. Thanks in advance for any help, and please let me know if there's any key info I've left out!
Machine: Samsung Chromebook XE303C12
OS: Version 38.0.2125.110
I have to devices here, both equipped with my core data application. The problem is, when I build it for device (development build), and sync it with iTunes to my 3 devices (2 iPhones 3GS and an iPad), the application works correct on one iPhone and the iPad.
On the other one, it doesn't return records (from a prepopulated sqlite database).
The device on which it is not working is not set up as development device, the other two are, but the correct profiles are installed and the application runs except for not fetching the records.
Any ideas because I've never seen anything like this before.
I've tried a restore with no success.
Solution:
I could not figure out what the cause was, but a restore and a setup as new device solved my problem.
The fact that all data in the backup was lost did not matter since it was a demonstration device and did not contain any important data created by using it.