Why some capabilities are disabled in Apple account - Certificates, Identifiers & Profiles - configuration

When I create an app identifier in my Apple account, I find some capability disabled. Some capabilities can be checked/unchecked but others are not. For example App Group, Push notification are disabled.
How can I fix it?

/Certain entitlements are only available when you use explicit bundle IDs for the app. Ensure that when you are creating your bundle ID for the app that you do not use the wildcard (*) at the end of your bundle ID.
From Apple's Q&A on the subject:

Related

Magento 1.9 / OpenMage: Built In Mechanismm To Pre-select Bundle or Configurable Product Options

After reading this thread which appears to be discussing adding configured bundle products to the cart (using URL params), I remembered one of my clients asking me recently if it was possible for their sales associates to send clients a link (via email for example) to a bundle product that's preconfigured.
The use case is that a client could be on the phone asking about a specific bundle or configurable product. When the sales associate sends a link, they then have to confusingly explain to the client that they need to select some options.
What would be better is if the sales associate could send a link with preconfigured bundle (and or configurable) options preselected using URL parameters.
I'm a developer and so I'm happy to write something. But has anything like this been done before? Perhaps an old 1/2 finished extension or any pointers to save some time?

Transfer Chrome WebStore Extension using Group Publisher Account Between Workspaces

Currently I work on a Chrome extension published but unlisted in the Chrome Webstore. Our organisation uses Google Workspace and the extension's owner is bound to a group in the Workspace which Google calls using a 'Group Publisher Account'. We ship the extension to support another application and because of this our documentation describes how to manage the installation of the extension via the Extension ID (the alpha numeric UUID that identifies the extension)
Because of various corporate changes, we'd like to transfer the ownership to a group in a different Google Workspace. In the developer console when we tried to unhook the group publisher account it said that we must unpublish all extensions. While the extensions not being available is a little inconvenient its not the end of the world. However, what we're now concerned about is that unpublishing the extensions, removing the group publisher (at which point ownership will revert to an individual account in the group based on some rules, we think we can arrange for this to be an individual in the new Workspace by adding them as a member of the original Workspace group), and then republishing may cause our extension ID to change. Which is something we really need to prepare for.
Does anyone have an experience with doing this, that could warn us of any landmines we might step on here?
You'll want to use the One Stop Support form to initiate the transfer request.
My item (extension, app, or theme)
I want to transfer my item
The form itself calls out a few caveats to be aware of. As of Feb 14, 2022 it stated:
Please make a note of the following information -
After submitting this form, you will need to confirm the transfer from the original publisher email address
The destination account needs to be registered before submitting this form. A $5 registration fee is required for the registration. Learn more.
Ensure you give the correct account details
Only items that are published and without any violations will be transferred.
Transfers can take up to 7 days
Transfering an extension does not have any impact on end users. The extension ID will be retained, existing installations are not affected, and users will continue to retrieve updates as expected.

What is the difference between advertising identifier and app instance id?

I use Firebase Analytics on a mobile app, and try to track user property by advertising identifier. But now I also use appInstanceId for app user identification.
I read the official document about tracking advertising identifier on Firebase and understand about what kind of data we can track.
But I don't understand about the difference of definition between appInstanceId.
Are these two id generated in a different way? (I think advertising identifier is device-specific, while appInstanceId is app-specific. Is it true?)
Can I track the advertising identifier itself on Firebase and check the value of it? (appInstanceId is automatically tracked, and we can export the value to BigQuery)
Yes, advertising identifier is device specific. If you have 2 apps on the same device, they will report the same advertising identifier unless the user set limit ad tracking to true on their iOS device. App instance ID is unique among apps on the same device, and it doesn't depend on the advertising identifier. On iOS, you can get it yourself using AdSupport framework. Firebase console doesn't show you the raw data of IDFA so you might want to track it using custom user property and query it using Big Query.

Detect Toast Notification from the particular application

I have two application both of them send toast notifications, I want to detect the Toast Notification from the particular application.On search I findpublic ToastNotificationHistoryChangedTrigger(string applicationId),what would be the application ID during development?
What would be the application ID during development?
Here is the MSDN documentation for the parameter:
The identifier of the app for which you want to create an instance of
the ToastNotificationHistoryChangedTrigger class.
More searching on MSDN, here is more info about application identity, which will appear in the package manifest:
<Application Id = An ASCII string between 1 and 64 characters in length.
The unique identifier of the application within the package. This
value is sometimes referred to as the package-relative app identifier
(PRAID). The ID is unique within the package but not globally. There
may be another package on the system that uses the same ID. The same
ID cannot be used more than once in the same package.
So it means both applications need to exist in the same package. I don't know how is that possible right now and I doubt that it is your case. Most likely, you have multiple packages, one for each app. In this case, you can use AppServices to communicate between the two apps.
Edit
Here explains about multiple app packages, it is supported for side loading and not the store.
You can create a multi-app package for side-loading, just not to
deploy through the store. When the user installs the package they'll
get all of the apps, and the apps will all share the same security
context, local data, etc.

sharing a users folder as admin

Trying to figure out if I can do the following via the box-api.
authenticate as an enterprise admin
lookup a user (in our case a special box user named "group_xxx" where this account will serve as a non-person shared group like "group_math_dept", "group_engineering_dept", etc...).
query for the root folder info for a given user-id (perhaps "GET /users//folders/0"
(tried that it doesn't work).
View the list of enterprise users with whom the given folder has been shared.
Modify the list of enterprise users with whom the given folder has been shared.
What I'd like to do is develop an app to delegate admin of these special group accounts to an appropriate individual in the given group. We can maintain who admins what locally. I can authenticate as one of our Box Admins (i.e. I have working code for steps 1 and 2). However, I don't see support in the API v2.0 doc for steps 3, 4, and 5.
Am I missing anything?
Unfortunately my understanding is the same as what you've found; that account and meta operations like steps 3 through 5 are not currently supported through the API.
UPDATE:
Looking at Box's developers blog it looks like functionality for steps 4 and 5 were actually just added, but are not yet in the documentation.
http://developers.blog.box.com/2012/09/10/v2-api-updates-keep-rolling/
Box actually has some more enterprise/admin API methods in private beta. Those are made accessible to early testers for a controlled environment, and include methods to perform operations on behalf of other users with administrative privileges.
If you're interested, feel free to email api [at] box [dot] com to discuss the testing of beta methods.