You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/pages/admin-ui-sdk/app-registration.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn about registering your app in the App Registry
5
5
6
6
# App registration
7
7
8
-
When the application on App Builder is ready to be published, a registration to the Adobe Registry is required to add a menu in the Admin Panel.
8
+
Your app must be correctly configured with Adobe App Registry to use the Admin UI SDK to create a custom UI in Commerce. You must perform the following steps before submitting your app to be published.
Copy file name to clipboardExpand all lines: src/pages/admin-ui-sdk/troubleshooting.md
+15-5Lines changed: 15 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -9,19 +9,29 @@ In this comprehensive troubleshooting guide, we'll help you navigate through com
9
9
10
10
## App menu is missing in the Commerce Admin
11
11
12
-
It's common to have the App menu missing from the Commerce Admin Panel menu when:
12
+
It's common to have the App menu missing from the Commerce Admin menu when:
13
13
14
14
***The app is not correctly published in App Builder.** Go to the App project in the developer console and check that the Production workspace has a status of Published. If this is not the case, request an approval to publish and test again once the application in Approved.
15
15
16
-
*. **The latest changes are not correctly deployed and published.** Make sure to deploy the latest changes using `aio app deploy` in the correct `org/project/workspace`.
16
+
***The latest changes are not correctly deployed and published.** Make sure to deploy the latest changes using `aio app deploy` in the correct `org/project/workspace`.
17
+
18
+
***The `Magento_AdminAdobeIms`module has not been enabled.** Run the following command from the Adobe Commerce command line to check the status of this module.
19
+
20
+
`bin/magento module:status Magento_AdminAdobeIms`
21
+
22
+
If the response indicates the module has not been enabled, run the following command:
23
+
24
+
`bin/magento admin:adobe-ims:enable`
25
+
26
+
[Configure the Commerce Admin Integration with Adobe ID](https://experienceleague.adobe.com/docs/commerce-admin/start/admin/ims/adobe-ims-config.html#) provides additional information about setting up Adobe Identity Management Service (IMS) on Adobe Commerce.
17
27
18
28
***The registration of the menu is not correct.** Make sure that you defined the correct `menu` method with a `getItems` function that returns an array of the menus to register.
19
29
20
30
* To make sure your registration is correctly deployed, navigate in your browser to `<appURL>/index.html`. You can find your application URL in your project workspace in the Adobe developer console.
21
31
22
32
* Check the elements in your browser developer tools and look for the script `src` in the body. It usually has the format `index.<random>.js`.
23
33
24
-
Replace in the URL the `index.html` with this javascript to access its content. Search for `getItems` for example and make sure the registration defined in your app is the same one you see deployed.
34
+
Replace in the URL the `index.html` with this javascript to access its content. Search for `getItems` for example and make sure the registration defined in your app is the same one you see deployed.
25
35
26
36
## App page is not displayed when accessing the menu
27
37
@@ -32,9 +42,9 @@ An app page is not displayed when the `extensionId` specified doesn't match with
32
42
*`extension:getId` method that returns a string with the `extensionId`.
33
43
*`page:getTitle` method that returns a string with the page title.
34
44
35
-
*. Check the `extensionId` is the same used in the registration to identify correctly the application with a unique name.
45
+
* Check the `extensionId` is the same used in the registration to identify correctly the application with a unique name.
36
46
37
-
## Timout error
47
+
## Timeout error
38
48
39
49
Timeout errors can occur when a process or operation takes longer than the specified time limit to complete. The retrieval of extensions from App Registry has a timeout set to 10000ms.
0 commit comments