I have an old project integrated salesforce Mobile SDK (version 4.3.1), which is working fine on Xcode 8.1.
Now I want to update to make it working on Xcode 13 (or Xcode 10.1).
When I'm updating pods it is throwing more than 500 errors. Any help or link which can help me.
NOTE: Can not make this project from scratch, since it has a lot of functionalities.
Related
I am developing an app for iOS and also using Mac Catalyst to run on my Mac. The app runs fine on my iPhone but always shows an error on Catalyst. The code used to run fine before updating to Big Sur Beta 6 from Beta 5. Here's a screenshot of the error: . Also the error in code blocks for anybody who wants to copy it.
The operation couldn’t be completed. (OSStatus error -10670.)
Domain: NSOSStatusErrorDomain
Code: -10670
User Info: {
"_LSFunction" = "_LSOpenStuffCallLocal";
"_LSLine" = 3664;
}
--
System Information
macOS Version 11.0 (Build 20A5364e)
Xcode 12.0 (17210.1)
https://github.com/MysteryCoder456/VegieMato/tree/backend is the GitHub Repo if anybody wants to reproduce this (i.
Faced same issue after upgrading to macOS 11 Beta 6. Reported bug to Apple but meanwhile found workaround - Select Product in Xcode, select 'Show in Finder'. Launch it from Finder. Additional step, hopefully Apple will look into it.
The problem is solved with new Mac OS 11.0 Beta (20A5374g).
If your catalyst app has multi-window support, you may still need to kill your existing app before launching the new one.
I also had the same problem. (I say had, I guess I still do, however I have a workaround) My App had been developed as iOS / iPadOS with Mac support. All has been working great throughout macOS 11 beta builds. Until today that is, when I, as you, updated to Beta 6. Upon attempting to run for macOS target I get the same error as you have posted.
After some googling I found https://www.virusbulletin.com/uploads/pdf/conference_slides/2015/Wardle-VB2015.pdf and had a go at simply opening the app directly from the build folder. Hey presto, it opened without any problems, I even cleaned out the build folder and built it again to make sure.
This would appear to be a problem that the next version of Xcode beta should fix. Until then, unless anybody can suggest a better fix, this will have to suffice for me at least :-(
Sam
-10670
I was having this same error code upon installing a Developer ID Distributed, Auto Signed version of a catalyst app on a test machine, non M1 Chip, Mac Mini(Late 2014) with MacOS Version 12.0 Beta installed.
The solution was to close the previously installed version of the app. Before opening the new version that I Airdrop over to the test Mac machine.
I have several projects developed in Xcode 10, but now Apple is saying (April 2020) that will not accept apps developed in Xcode 10, only Xcode 11. Is there any compatibility problem ? All my projects will compile properly in Xcode 11 ?
Is there any compatibility problem ? All my projects will compile properly in Xcode 11 ?
Try it and see? You don't really have a choice in the matter if Apple is going to stop accepting your Xcode 10 apps, so you might as well get started.
You can have multiple versions of Xcode installed at the same time. The best plan is to download Xcode from the developer site instead of the App Store, and rename each one with its version (e.g. Xcode-10.1, Xcode 11.4, etc.) so that they can all exist in your /Applications folder at the same time.
Xcode 11 will happily open your Xcode 10 projects, and everything should be fine. You may need to update some project settings to whatever Xcode 11 recommends, and your code will probably benefit from updates for the latest macOS or iOS versions.
What Apple will require is that apps be built with the latest versions of their platform's SDKs in order to be submitted and approved to be distributed through the App Store. They have extended the deadline for this to June 30, 2020 at the time I'm writing this (as you can see here).
This means that you need to make sure your project can be built using the latest SDK major versions. Make sure to open and build your projects using Xcode 11, which has the latests SDKs embedded in it. If your project fails to build, it can usually be because of 2 things:
The new SDKs API have changed and code that you wrote a while back might now be invalid. Go through the issues found by Xcode and update your code to make it work with the latest API.
The Swift language itself might have changed and code that you wrote a while back might now be invalid. These type of issues can be avoided by setting a specific Swift version to be used on your project in its build settings. Migrating your codebase to the latest Swift version (the one that's bundled with Xcode) might not be mandatory, but I'd recommend you do it if it involves just minor changes.
if after doing this, your project can be built, you should be good to go.
Using xcode 5 with my upgraded iOS 6 to iOS 7 app, I have run into issues with upgrading third party frameworks and adding third party frameworks which 'break' other seemingly unrelated frameworks. For example, I tried to upgrade the Crittercism framework which was already included in my project and it broke my Stackmob framework with the result that the project build failing because it couldn't find the Stackmob framework even though it was in the same location before the Crittercism upgrade. I had to remove the Stackmob framework first, then upgrade Crittercism, then reinstall the Stackmob framework, then the build succeeded. Another example, is when I tried to install the Parse framework. That broke my PushIOManager framework resulting in the project build failing since it was unable to find the PushIOManager framework even though it was in the same location as before I did the Parse installation. This is after doing clean and builds on the project. This does not seem to be happening with the built-in frameworks when I add them to the project. What's weird, is that I tried doing all this on an iOS 6 copy of the app using xcode 4.6 and everything worked fine, no issues whatsoever. I was just wondering if anyone else is running into similarly strange issues with their upgraded iOS 7 app and xcode 5. Or if this is just some weird stuff that's unique to my app.
I followed this link http://wiki.developerforce.com/page/Getting_Started_with_the_Mobile_SDK_for_iOS#Working_with_the_SDK
to as to integrate my iOS App with the SalesForce. Now while creating new project I can't se the Native Force.com Rest App Template in New Project Wizard, instead only Hybrid Force.com App template is been shown.
Help Appreciated.
I recently solved this problem by Updating to OS X 10.7.3 and doing a fresh install of XCode 4.3.1, then re-installing SalesForce. After the re-install, the REST template was right where it belonged!
Make sure you set the XCode directory so that SF knows where to put the files, otherwise the install will hang!
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
I hope you get it solved!
Salesforce Mobile SDK for iOS was updated to version 1.1 this past week. Among the fixes were updated instructions for installing the SDK on Xcode 4.3. The old install script doesn't work for the latest version of Xcode so getting the latest source code from Github might solve your problem.
As the the Question asks,
I currently sport xcode 3.2.3 with iOS 4.0.1 but I want to test on my iPhone which is stuck on 4.0.2
Thus I cannot do so until the SDK for 4.0.2 is accessible from xcode.
Where can I download a patch update from 4.0.1 to 4.0.2 because the iPhone members page seems to only link me to the package including xcode 3.2.3 with iOS4.0.2 SDK
I don't want to download the whole thing because it's > 2.5 gigs and my New Zealand internet Connection is shizenhouzen.
I can't restore to a previous version, because for some reason I only have a previous back up of the iPhone on my now defunct windows PC.
I'm afraid you have to download the entire SDK - Apple do not provide 'patches' (4.0.1 to 4.02, for example) AFAIK, and I'd be nervous about downloading anything that claims it is a patch.
It's a common grumble, twitter is a fun place when apple push these .1 SDK updates out :)
You do have to download the whole thing to upgrade. It really sucks. :-(
I wish I could remember to download the SDK before upgrading my devices.
You can still build adhoc releases of your app and install them using itunes if you're in a real bind - it's just the debugger, console viewing and automatic installation of builds that won't work at all.