ok - it is indeed not yet available in 2.0 according to Analytics docs: https://www.adobe.io/apis/experiencecloud/analytics/docs.html#!AdobeDocs/analytics-2.0-apis/master/migration-guide.md.

Hi @Urs_Boller ,1. For app layout, you could leverage the Flex and Grid components in React Spectrum.https://react-spectrum.adobe.com/react-spectrum/layout.htmlhttps://react-spectrum.adobe.com/react-spectrum/Flex.htmlhttps://react-spectrum.adobe.com/react-spectrum/Grid.htmlIn your case, Flex would b...

Hi @Urs_Boller , the Firefly SDK for Adobe Analytics only supports the 2.0 API.If the functionality you need is only available in 1.4 API, not 2.0, you would need to make the HTTP requests using `node-fetch`.Which functionality of AA API that you want to use?

Awesome, thanks for confirming. Great that it works!

@eldhov19157560, I don't think you need additional permissions to view the submitted app. Could you please confirm that you selected the same org in which the app was submitted for approval before?I will follow up with the team if you still don't see the app despite correct setup.

@eldhov19157560 , does your account have access to more than 5 orgs in console? If that's the case, you are not able to see the orgs in My Exchange. While our team is working on a fix for this issue, workaround could be that you create a new admin account in the org you want to approve the app, and ...

Hi @eldhov19157560 , to approve / reject an app, you need to do it from Adobe Exchange (https://exchange.adobe.com/my-exchange.html).You should be able to select the org, in which the app is available for review.

yes, that's correct.

Hi @eldhov19157560 , the URL you got in the terminal upon `aio app deploy` is only for testing the app on Adobe Experience Cloud (ExC) Shell.To have your app visible in the "Project Firefly Apps" dashboard, you would need to publish it through Adobe Exchange. While we are working on the documentatio...

Hi - the error you got "Request defines parameters that are not allowed (e.g., reserved properties)." is due to the fact that you may have set some params in the "inputs" list in your manifest.yml, and you provided the same param in your request to the web action.