The MSDN page for CurrentApp.appId is here.
In a typical application the property comes back in the format 00000000-0000-0000-0000-000000000000, and precisely that number if you're running an app that is not in the Windows store.
Once in the Windows store, it gets a real number, and my question is: Is there anything that would cause an appId to ever change? Perhaps as versions of the app are updated, or if the app is renamed?
The AppId will not change unless you remove the existing app and republish.
I do not have a source for this, but it is the same process from the Windows Phone Marketplace/Store. The ID is used in many places.
The direct link (URL) to your app
Used by the Store app to identify which apps have an update
Used by Visual Studio when creating/uploading packages
...
Changing the Global Unique Identifier is totally against the point of a GUID. If it changed, many things would break. The ID does not change when updating the app, it remains the same.
Related
advertisingIdentifier is different for apps from the same vendor.
Of course there is an ability to add apps into group and share some "unique string". But I suppose that there must be some easier way.
I also read about "Uniquely Identifying a Macintosh Computer" but I suppose that such apps are rejected in mac AppStore.
In our app we access the system serial number. We use it to try prevent multiple users using the same account + for debug purposes (so not for ads or anything, our app has none).
We also have code to access the hardware uuid but that code isn't actually used at the moment, but it is in there, so not sure how deep Apple checks. So you might be able to use this one too. As an additional step you could hash either of these (or hash them appended or something).
This app has been on the AppStore for a long while now, and was never rejected for this reason. So I'd say accessing this data on macOS should be ok (for now) depending on usage and safe to submit to the app store.
Keep in mind that in some rare cases, the serial number will not be available. In that case we store a random string in UserDefaults.standard and use that cached value in the future.
Since this information won't be available to your 'other' app(s), this workaround won't work for you though.
I have several applications in the Windows store and I've stopped supporting some of them.
I don't want to just unpublish them or make them unavailable, but completely get rid of them.
How can I permanently remove them so that their names can be reused again by others.
Thanks,
robcsi
Currently, for the app you have never submitted to the Store, you could click Delete this app in the upper right corner of the App overview page, which also releases the reserved name so that you and someone else can use it. However, you’re not able to delete an app from your dashboard once it’s been published. You can make it unavailable or select Hide this app and stop selling in the Distribution and visibility section.
If you just want to reuse the name of them, you don’t need to permanently remove them. You could go to the Manage app names page in the App management section for any of your apps in the Windows Dev Center Dashboard. You can click Delete to remove the name you want, which means this name will immediately be available for someone else to reserve and use.
But please note that your app needs to have at least one reserved name. So you might have to reserve a new name for them before deleting the old one.
More details, please see Manage app names.
I have already submitted an app (v1.0) now i wanna update my app. here, i got confusion. There in the windows developer center, two options are available.
Replace or Add New. Which one I should give to update my existing app ?
To update your app, you should use Replace.
Add new allows you to associate multiple XAPs with the same app GUID (for example, if you want to publish two different binaries for a single app: a WP7 version and a WP8 version).
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.
I would like to be able to change the OSX services that my application provides based on the current user's preferences (like adding more, changing the name,...). This basically means modifying the Info.plist (NSService key), but I don't think it is a good practice when an application modifies its own Info.plist while running, right? (At least based on few searches here). Is there any other option how to get this functionality?
I guess it should always be an external entity who does modify the Info.plist? So far I can only think about providing a system preference bundle which will do the modification in the actual app? Do you have any ideas?
Thank you
One way would be to install a service in ~/Library/Services that provides the services, and edit that application's Info.plist from your main application.
Of course, that should be an explicit action, so the user (hopefully) knows to delete the service if they delete your application. And you should document that procedure on your product's support web page, just in case they don't.
Here's a small twist to the previous recommendations, create a separate app that handles the service and bundle it within your Resources. When you want to enable the service, instead of copying the file over to ~/Library/Services, create a symbolic link within the ~/Library/Services folder that points to the app you bundled in your Resources.
This way if the user deletes your application, all that will be left behind is a symbolic link pointing to an invalid location. Does less arm than actually leaving the app behind and will have the added benefit that the service will no longer be available (since the info.plist will have been removed when the user deleted your app).