I am using the Salesforce iOS SDK for Customer Support (https://github.com/forcedotcom/ServiceSDK-iOS). With the update to iOS 13 the view disappears right after showing. I cannot edit the code so I have to ask if someone has the same problem and worked out some workaround.
Yes, I'm in the same boat.
Here's an official statement from Salesforce saying that a new SDK should be available starting October 7.
There was a discussion about this on GitHub also, but they've removed issues from their repo recently.
I guess we'll just have to wait until next week.
Related
Problem
In Xcode (Version 13.2.1 (13C100) and the latest beta, Version 13.3 beta (13E5086k)), trying to login to my Apple ID results in the error, Unexpected nil property at path: 'Provider/attributes/developerTeamId'. Has anyone got a solution to this?
Observations
this happens on multiple computers. So don't bother resetting your system. I am trying to use an older version of Xcode now. However, this might be an API issue (data sent back from Apple servers) which isn't structured well for Xcode.
this affects accounts with multiple teams.
Apple has fixed the issue
Apple has fixed the issue, you don't need to update Xcode, since it was an issue in their backend. I've emailed the Apple developer support as this seems to not be an isolated issue. Trying the latest beta of Xcode, Version 13.3 beta (13E5086k) did not solve it. This seems to have happened 1 year ago as well.
Temporary workaround
I've noticed that this only happens to me if my Apple developer account belongs to multiple teams. So I left all the teams except 1 in my alternative Apple ID.
Go to App Store Connect's "Users and Access"
Go to App Store Connect > Users and Access > People > "YOUR NAME" > Scroll down > "Leave team".
Leave the team
Scroll all the way down, and click "Leave Team". You need to leave all the teams except the one you're working on. Obviously, you'll need an invite later to work on those teams again.
Alternative
Alternatively, create a new Apple ID and invite that one to the team you need to develop for. Fortunately for us, Apple only broke Xcode, and not developer.apple.com. 😅However, you'll need an Organization team, not an individual team.
Have the same problem. I had mac In Xcode (Version 13.0 (13A233)),(MacOS BigSur 11.6 (20G165))when i trying to upload my app to Test Flight .
I think if your apple developer account have multiple team id,May be Xcode unable to find correct app id.
I found one solution i install transporter app and login through any apple id and select team id export your app and add .ipa file .
Hola it works
After writing to feedbackasistant the problem was fixed for me.
Xcode Version 13.2.1 (13C100)
I've been testing my Xamarin app on IOS 14 beta 5, and I saw that there is a new privacy feature, where you can control what photos to share with your app. I am using an UIImagePickerController to display the photos, but right now I get all photos(even though I selected only some to be used by my app), and when trying to select one that was not in my selection, the app crashes.(PHImageManager.DefaultManager.RequestImageData return back wiht error code -1 in this case)
My question is, will there be some new features in the next Xamarin iOS framework to support this functionality?
Because I've been reading on the IOS developer forum that they are planning to have a new PHAuthorizationStatus-> PHAuthorizationStatusLimited, and maybe based on this status, we could filter our pictures.
Or is there currently a way to filter the photos I present on my UIImagePickerController?
Thanks
Apparently, in Xamarin.iOS 13.99.0, they introduced the new status: PHAuthorizationStatus.Limited, and also a new type PhotosUI.PHPickerViewController(since UIImagePickerController is obsolete, we will need to use the new PHPicker ).
More details on added or changed types are found here:
https://learn.microsoft.com/en-us/xamarin/ios/release-notes/api-changes/ios-13-20-2-13-99-0
If anyone needs to use this version of Xamarin.IOS, they can find it in Visual Studio->"Check For Options"->"Xcode 12 Preview" (Visual Studio 2019 For Mac).
Maybe someone will find this useful.
I am currently testing the Apple News JSON format using XCode / News Preview / Simulator and randomly running into a new error that was not occurring prior to today.
I am attempting to load the article.json file into the News Preview app (it's been working up until today). The article.json file gets successfully loaded with no errors in the console but the Simulator is claiming that the channel is not available for me. Here is what the error message on the Simulator reads:
Channel Unavailable
This channel isn't currently available in your region.
The News Preview and Simulator were working just fine until today. I have tried re-installing XCode and News Preview (and Simulator because I re-installed XCode) but the problem persists. Other colleagues of mine are now experiencing the same problem.
I tried also clearing all the content in the Simulator and tried wiping the device clean and also tried going to the "Debug" menu in Simulator and setting the Location specifically there, as well, without any success.
Is there a way to fix this or is there a way to know if there was a recent developer push to the Simulator code base?
Just to add a bit more detail, I am attempting to load the official Apple News article preview files, not my own article.json files (I tried loading my own json files, as well).
Any help is appreciated.
Hey I also just had this issue and have been troubleshooting since yesterday. Not sure what is causing it, but it only happens for my on devices simulators from iPhone 7 and newer.
Try running the preview on iPhone 6 or an older-gen iPad, etc... that's working for me.
The solution on only one of my machines was to enter the Publisher ID into the News Preview application, which is the first thing that is asked when launching the News Preview app. After entering the Publisher ID, everything seemed to return to normal - for all of my colleagues and I.
See my comment above about my new macbook and the new problem it is having.
I am currently running iOS 10 beta 8 with Xcode 8.0 beta 6 and the custom sound does not play when I receive a push notification with the correct payload.
I have verified the payload and it is in the correct format per the apple documentation:
{
"aps" : {
"alert" : "You got your emails.",
"badge" : 9,
"sound" : "bingbong.aiff"
},
"acme1" : "bar",
"acme2" : 42
}
When I send the same payload to the same build on iOS9 the custom sound plays properly.
Does anyone know if there are any other changes in iOS 10 that I need to make?
This problem seems to only affect apps installed via Xcode. The issue persists even if you later update the app from a different source.
The solution is to completely remove the app, and reinstall it from TestFlight or the App Store.
In effect, this bug should not affect your end users.
Edit 2016-10-15:
Unfortunately it seems that I was mistaken. This appears to be a bug on iOS 10 that can, in fact, affect App Store apps also. If it is of any consolation, apps such as Facebook and WhatsApp are affected too. The solution is apparently to force restart your phone, but unfortunately there doesn't seem to be much we can do about it as developers.
Apple Fixed Issue:
Based on this comment, Apple has seemed to fix the issue in iOS 10.2
Try installing your app using Test Flight and after implementing initial process to update device token just restart your device.
You'll get what you have been looking for.
Credit goes to - binncheol
Having our user restart their device is correcting the issue for us.
This is an issue for us regardless of how the app was installed (TestFlight or from the app store).
There is definitely an iOS10 bug which still persists as of 10.0.2. It affects many apps including popular ones such as Whatsapp and Messenger. The workaround is just to power cycle the device, after which point the notification sounds are correct. It doesn't seem to matter how the app is installed.
I can't find any documentation of this from Apple (go figure) but there is more info here: http://thetechbeard.com/how-to-fix-notification-sound-problem-in-ios-10/.
As reported here lots of other people are having this problem. Hopefully Apple fixes it soon.
I uninstalled the app, turned off the real device, reinstall the app, and then the custom notification sound started working. It didn't work before I restarted my device XD
I just loaded Xcode 6 GM seed. Now I want to submit an update of my app.
Archiving works so far. But when I click "Submit", as soon as the upload loading bar appears Xcode crashes.
Do I need Yosemite?
I had to download the Application Loader from Apple because Xcode could not find it.
Do I need Yosemite?
No. Mine crashed the same way, so i uploaded my app using Xcode 5.1. It worked fine.
The Application Loader seems the only thing that works right now. Had the same problem, while uploading or even just validating.
Just export via Organizer and Upload via Application Loader helped.
I was faced same problem. Now it works fine.
Solution : Just accept new changed terms and condition from apple developer account and resubmit it.
Please Make sure you've accepted all of the new agreements & condition in the Member Center.
To check if you need to, you can go to the preferences -> accounts in XCode, and chose to view details of an account and attempt to refresh button. Here, XCode will warn you that you need to accept new agreements in the Member Center before you can refresh.
or just login to developer account and go to here https://developer.apple.com/membercenter/index.action
I was able to make Xcode work, but I had to go to iTunes connect and start the process there first by going "My Apps" and clicking on the plus sign. Fill in the info and hit save. Then try submitting with Xcode and it should work.
OK. Here's my $0.02.
1) Xcode 6GM crashes every single time for me. I am running 10.9.4. I have no idea how widespread the issue is, but it is 100% repeatable for me. I cannot use Xcode 6 to submit apps for review.
The crash happens during the upload. I have submitted a RADAR report and given crash logs.
2) I was able to submit using the App Loader. Here's how you do that:
2.1) In the Organizer, after you have done the Archive, select the latest archive for submit.
2.2) Instead of "Submit," select "Export."
2.3) Select the first choice (App Store).
2.4) Open the Application Loader.
2.5) Select "Choose."
2.6) Select the .ipa that you just saved in the export.
2.7) That will work. You may get a message teling you that the API file is too big for analysis. I got that for all 9 of the apps I just submitted. In my case, I ignored it.
I think they rewrote the whole application load from scratch, and that Xcode is still buggy as hell.
They had a deadline, and rushed it. It shows.
I expect both the server (Web) component and Xcode to apply patches soon.
In my case, I'm quite annoyed, as I had to rush out a fix for the arbitrary decision they made to change the way that the CLLocationManager works, which broke all my location lookups. The fix is simple, but there will be a period of time when I receive hate mail from the users that upgrade to iOS 8, and the app stops working.
Joy.
I just installed the official version from the App Store and now everything works fine.
I had the same problem. When XCode crashes during export or submit it means that you have non-valid certificate or provision profile in build settings.
Here is the solution:
Accept new changed terms and condition from apple developer account. (Just like Sandeep said)
Go to here to generate new provision profiles, for App Store & AdHoc (Tutorial)
Double click new provision profiles you downloaded to install them, and then XCode will never crash.
The problem is caused by XCode 6.0 does not handle provision profile migration properly. Developers should regenerate provision profiles for XCode 6+, but Xcode 6.0 fails to display this error message properly and crashes. (If you use XCode 6.1 Beta, it will display error messages for you, no crash. Then you will know that the problem is caused by "invalid"=="legacy" provision profile.)
After that, you can submit app and export Ad Hoc distribution for Testflight.