How can we set different API endpoints in Xcode Cloud for our project - xcode

I am working on a project where I need to choose between three end points for API:
.app
.cloud
.com
I am not sure about how can I do this while either archivng the app itself in Xcode without having to change the end point in a Constant file for example. Or achieve the same result in Xcode Cloud CI CD.
I don't see any option to set or choose API endpoints in Xcode Cloud

Related

Mac app: expand the app by adding extra bundles inside

I have a very big APP on MacOS , > 1 GB.
I want to create a miniature version of this app with minimal functionalities.
When user wants extra functionality , I want that extra bundles are added to this app so that it becomes equivalent to my original app.
How can I achieve this considering code sign and notarization issues.
I dont want to place these bundles outside the app so that after expansion my minimal app becomes exact copy of original bigger app - otherwise would need to create separate update pkg for both the kinds.

XCode UI Testing: Can I use UI Testing scripts to access the documents directory of the target app?

I am testing an iOS app using XCTest Framework. I have to access/read projects from the Documents directory of the target app. Since XC Framework installs itself as a separate app on the simulator, I cannot access the directory as the app runs in sandboxed environment. Is there any way to access the directory apart from uploading the files on Cloud storage or using shared storage by making a common App Group (both of these options do not look feasible as the project size is too large and the Common App Group method seems to be complicated)?

Xcode Server CI to TestFlight

I've set up an OS X Server and Xcode Service. After this, I've created a Bot for my iOS App.
The Bot is working fine, but I'm asking me now, how could I make the Bot uploading the builds result automatically to TestFlight?
Take a look at fastlane, in particular pilot. In it's simplest form once you have everything configured you can call pilot upload to upload an ipa in the current directory.

Cleanest way to upload image to S3 from Mac OS X app?

I have been trying to find an easy solution to upload a small image (500px) to S3 from a Mac app I am building.
The mac app is an OS X version of an iOS app I have already built. The only interaction I need to have with AWS is to upload images so I am just looking for the best practice method for doing this.
Is creating a PHP script to do the job on the EC2 instance the best way to go about this since there isn't an AWS SDK for Mac?
I have created an OSXified version of the iOS SDK here. I have added a scheme to build only the modules (AWSCore, AWSCognito and AWSS3) you need for S3 interactions. Once you build, locate the Products directory in finder and you should see the 3 .framework files you will need to add to your OSX project.
From that point onwards it is the same as using the iOS library, instructions for which are provided here (Getting started with Swift/Objective-C sections).
When using in your own project make sure you add a build phase for copy files and add these frameworks there. Lastly turning on codesigning will prevent you from having to interact with Keychain Access everytime you run your app.

How can I pull the latest Cloud Code?

I need to use the command line tool provided by Parse.com to get the latest Cloud Code from my application, how can I do that? I'm working with a team and can not overwrite the existing Cloud Code.
You can now download deployed Cloud Code through the CLI.
Through the command prompt (on Windows) type:
parse new
Parse will then ask you to provide your user credentials. Once provided, the command prompt will ask, Would you like to create a new app, or add Cloud Code to an existing app? Choose (e)xisting, and you will be provided with a list of apps you currently have access to to choose from and the rest is cake.
Make sure you update the Parse CLI in order to get this work by using:
parse update
You can use parse download command:
parse download -l [location]
Works great in our team. For more information about the command use
parse download --help.
Note: if no location is provided, code will be downloaded to a temporary folder.
UPDATE: You can now download your deployed code easily with the Parse CLI:
parse download
HISTORIAL: Previously (May 11, 2015) there are only 2 ways to get cloud code deployed by someone else on your team:
You get a copy directly from your teammate
You go to the Parse.com Core dashboard, tap on Cloud Code (below the Data section with all the classes), then click on each file on at a time and copy/paste the window contents into a file with the appropriate name.
Neither of these are ideal solutions.
Ideally, your team would use a two-part solution like this:
A version control system (like Github or similar) that keeps track of your most recent version
A dev mirror of your Parse.com app that gives you a sandbox for testing changes to the code

Resources