Why do I not see "Delete App" in Test Flight for my app - app-store-connect

Why cannot I delete my app from Test Flight?
I am the Team Agent.
The App is in "Prepare For Submission".
I do not have any Builds (I deleted them).
I do not have any connections to Game Center or anything else that I need to remove in order to be able to delete the app (as best as I can tell).
The app has never been to the App Store.

Related

Testing MS Teams app in a different organization

We've created a teams app and would like to test it within a different organisation as a pilot. We can see 2 ways of doing this, either submitting it to the partner center store or getting the admin within the pilot company to upload the app package themselves (such as in the link below).
https://learn.microsoft.com/en-us/MicrosoftTeams/manage-apps?toc=%2Fmicrosoftteams%2Fplatform%2Ftoc.json&bc=%2Fmicrosoftteams%2Fplatform%2Fbreadcrumb%2Ftoc.json#upload-an-app-package
Does anyone have any recommendations for this or any workarounds? We're unlikely to have the app in a fully finished state (hence the testing) so want to avoid uploading it to the app store for anyone to download. It seems a little strange that there isn't an option to allow pilots more easily.
Thanks!
At the end of the day, it has to be put into either the main App store, or to the "company" app store so that users in that tenant can install it. To that end, the options you've listed are pretty much in line, but there are also other ways to get it into the tenant's "company" store. It will depend on their user policy settings though:
It might be enabled for users to upload apps into the store directly (in the Apps list in Teams on the bottom left there could be a "Upload a custom app" menu option). This is ideal if there are a lot of users who need the app.
If user side-loading is enabled, the select user(s) could install the "App Studio" app into their own Teams environment, and from there there are steps to open a manifest zip file and install the app personally or to a Team/Chat. If this is an app for a Team/Chat, that would be fine. If it's an app that users need to personally install (e.g. a 'Personal' Tab app) then each user would need to do this - fine for a small number of users, but not great for lots of users.

iTunes Connect demo account in existing live database for app submittal?

I'm submitting my first app through iTunes Connect. It is a social networking community so I have to provide a demo account for the submission. My app already has a live database of users as there is currently an active web version.
I'm new to this and confused as to how I should handle this. Should I be creating a demo account that will not show up in any other live user's search results? Are the testers going to be attempting to interact with other live users? I am assuming I will need to show the various functions of the app, like messaging and events. In that case should I be creating a few "demo" users for the testers to interact with?
Alternatively, should I be linking them to the development version and development database? If that's the case, then the build that I send them would only be a development build then?
I am confused on how this is supposed to work and can't seem to find any information to help?
In my experience, you'll need to give them the production version that will go into the store. So not the development build.
When we submit an app for approval, it seems to get installed and activated on a couple of devices, but nothing much ever happens. They barely use it, as far as we can tell. We can tell that it's installed and run. We have previously been rejected when the network connectivity wasn't working right, so we know that they do look at the app after it's installed.
I'd suggest you make them an account that looks relatively anonymous (or even "Test Account" which you real users are hardly likely to try to interact with). You could create another account and say "If you want to send a message, send it to account xxxx". We've never had them interact with our app enough to utilise the suggestions we've made.
If you have an active / inactive flag, you could think about making these accounts inactive once the app is approved, then re-activating it when you next want to submit your app.

Are there any update frameworks for iOS apps?

I need to be able to update my app from within the app itself. I know Sparkle works for Mac Apps but I can't seem to find any for iOS.
Edit: I am not asking how to bypass the review process. I was thinking that there might be frameworks similar to Clutch.io that allow updates to images/documents/etc from within the app. Or things like UrbanAirship that manage in app purchase data that allows an app to be extended from the app itself.
You can't replace your app with an updated one (except through the App Store) and you can't replace parts of your app with updated parts (that would make your app's code signature invalid); you can only update stuff that's outside of your app's bundle.
You can't update the app binary yourself, the system is responsible for updating all apps.
Though, if you just want to update some data in your app you can do that for sure.
Here is what I was looking for:
http://code.google.com/p/cooliris-toolkit/
It has a class called RemoteUpdater which allows me to download zip files of images/data or whatever I like to extend my content.
Depends on your needs. If you dont want to see the app you can also do an Enterprise Deploy.
Used by corporations to distribute apps to their clients or employees.
Needs a separate Apple account which costs more.
Uses same process as deploy to appstore
Archive > Distribute > create ipa/plist > copy these to webserver with html page with link to plist and user clicks on link from Safari on iOS Device and it installs.
Going back to CArpp Store review process after that is painful.

iCloud update policy on CoreData in development and production mode

as specified in the subject I am developing un application that made use of CoreData and its built in iCloud feature.
Whenever I connect my devices (an iPad and an iPhone) to xcode and run the application, I can see after few minutes the log of CoreData updating data. In both devices on iCloud section, I can see my application full entitled for iCloud.
First question: how often are iCloud content pushed (or pulled) to devices ? Is there a way to force this ?
Second, I noticed that the devices, once disconnected from Xcode, doesn't update their data anymore.
While if plugged again and run the app, the data get updated.
So the question, is iCloud in development mode (the app is not yet submitted to App Store) working only trough xcode, and if yes why ?
Or am I doing something wrong within the objective-c code itself ?
thanks
The updates are getting pushed to iCloud servers whenever you save CoreData moc.
The updates are getting pushed from iCloud to device automatically. There's no way to force it as far as I know.
It can take from seconds to dozens of minutes for an update from iCloud to appear on your device (also depends on your connection speed). Apple doesn't give any guarantees on when it will actually happen.
I haven't seen any difference in iCloud behavior whether app started fom XCode or not. Check your code and UI updates base on iCloud pushes.

How can I synchronize items with the cloud while my app is in the background?

In my iPad app, the user can enter data online or offline, storing the data in SQLite, and when the user goes online, he hits a "sync" button, whereupon the data will be synced up to the cloud.
If the user enters data offline, the data persists in the local SQLite DB. If the data is not yet synced, I set a badge to the number of records pending sync.
When the user starts up his iPad, he should get some alert on startup saying "There are 5 records pending to sync." Then all the pending records will be synced, without opening my app.
Has anyone come across a similar scenerio? Does anyone have any idea how I can do that?
Before iOS 5.0 it was not possible to synchronize data with your application when the application was not running. However there were some scenarios when the app could e.g finish a download when the App was terminated but this background-processing is rather limited.
Now if you want to sync to the cloud and have the same data available on another iOS device or on a Mac app then I guess iCloud might be exactly what you are looking for.
So a possible scenario with iCloud might look like this:
You have your iCloud enabled App installed on two iPads
On both iPads you are logged in with your iCloud account (this has to match since iCloud is tied to a given Apple ID
When your App stores some data on iPad1 it will automatically be synced to the cloud
On the same time this data is downloaded to the iPad2 (which has to have internet connection) while your application is not yet launched. This is only possible with iCloud
When you now start your App on iPad2 (even if it is now offline) you will have the current data available within your App.
However, if you are running your own server backend, and maybe need more control over the data on the server, iCloud might not (yet) fit your needs there. You might want to check out the documentation or the sample code for iCloud: iCloud for Developers (Apple Developer Account required)
If you chose not to use iCloud then there is currently no way that you can sync data while your application is not running.
Edit:
A scenario without iCloud could look like this:
You enter Data on iPad1 while offline and set the badge to the number of unsynced items
Later you have internet connection, so you start the app and the items can be synced to your server.
Your server stores the newly arrived entries and could now send a Push notification to your App which is installed on iPad2 telling the user that there are n new entries on the server.
From that notification the user could now decide to open the app and the new items could then be downloaded to the iPad2.
If the user dismisses the notification then no data is downloaded until he starts your App the next time.