Hi @zihaof25182964 Did you try the Analytics example with React Native? That might help resolve your issues. We are actually in the process of releasing a new Swift-based Core, and an updated React Native wrapper to follow. These should be available in Q12021

Re: Tracking iOS Permission Request Alerts Ivan_Mironchuk - Adobe Experience Platform SDKs

Another helpful hint -> The Places extension holds the authorization status for a user in the extension's shared state. This shared state can be added as a Data Element in launch so that you can include the status in various workflows. The first image below shows how you can define a Data Element for Auth Status. The second image shows that you can use any data element in Launch workflows as a condition or part of an action (i.e. post back). How would this be valuable in a workflow? Let's say yo...

Re: Android Launch SDK not passing app ID on Adobe Analyt... Ivan_Mironchuk - Adobe Experience Platform SDKs

I would check to make sure that Lifecycle and Analytics are properly registered and initialized in the Android app, using the instructions for React Native: https://github.com/adobe/react-native-acpanalytics#usage Beyond that you may want to consider using Project Griffon (Adobe Experience Platform Assurance) to troubleshoot the data being sent from the app.

Re: AEP Mobile SDK support for Apple CarPlay and Android... Ivan_Mironchuk - Adobe Experience Platform SDKs

Hi @det2020 we do not currently have support for CarPlay and Android Auto. Extension support is on our roadmap, but will not be delivered in 2020.

Re: Create Mobile Property Without Launch? Ivan_Mironchuk - Adobe Experience Platform SDKs

As @Asheesh_P mentioned - Launch is available to any Adobe customer. You can use a bundled configuration as described here: https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/configuration#using-a-bundled-file-configuration , but using Launch is the best way to generate the configuration and offers a number of benefits going forward.

Re: Migration from SDK 4.x TO AEP Processing Rules Ivan_Mironchuk - Adobe Experience Cloud Mobile

Your processing rules are saved server side with the report suite. If you are sending the same data to the same report suite with the AEP SDK you should be all set.

Re: Looking for documentation: Mobile AA Analytics: does... Ivan_Mironchuk - Adobe Experience Platform SDKs

Hi @IsabelMayo You can find all of our Mobile SDK developer documentation here: http://sdkdocs.com Information specifically for Adobe Analytics - https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-analytics

Re: Help annotating PDFs from within iOS app Ivan_Mironchuk - Adobe Experience Platform SDKs

This likely belongs in the Adobe Doc Cloud community forum. Take a look at the Adobe Sign SDK https://github.com/adobe-sign

Accelerate your mobile application development with Mobile SDK and Experience Platform Launch Ivan_Mironchuk - Adobe Experience Platform SDKs

Giving your users a great mobile experience means constantly evaluating how they are interacting with your app and quickly responding with updates and optimizations. Based on these guiding principles, we built Adobe Experience Platform Mobile SDK from the ground-up to be modular, flexible and dynamic. Managing mobile SDKs through Adobe Experience Platform Launch brings a host of new features and capabilities that enable you to better engage with your users with meaningful personalization. The bl...

Update on end of support for v4 Mobile SDKs Ivan_Mironchuk - Adobe Experience Cloud Mobile

Last year, we announced that support for Adobe Experience Cloud's version 4 mobile SDKs would end on September 30, 2020. Customers were encouraged to migrate and adopt the latest Adobe Experience Platform Mobile SDKs at their earliest convenience. We have received feedback from multiple customers that the COVID-19 pandemic is disrupting mobile-related teams, projects, and timelines. In an effort to assist you and your team during this time, we are extending support for version 4 mobile SDKs to A...

Update on end of support for v4 Mobile SDKs Ivan_Mironchuk - Adobe Experience Platform SDKs

Last year, we announced that support for Adobe Experience Cloud's version 4 mobile SDKs would end on September 30, 2020. Customers were encouraged to migrate and adopt the latest Adobe Experience Platform Mobile SDKs at their earliest convenience. Recently, we have heard from multiple customers that the COVID-19 pandemic is disrupting mobile-related teams, projects, and timelines. To help with this disruption, we are putting our customers’ needs first by extending support for version 4 mobile SD...

Re: Multiple SDKs for mobile app push notification Ivan_Mironchuk - Adobe Experience Platform SDKs

While technically this is possible (using multiple solutions for push notifications) it is not advisable, as it may become difficult to understand when push messages are being sent and the frequency in which users are receiving them. If the third-party Push service does not support In-App-Messages, you could look to have Campaign setup for this and use the other solution for push.

Re: Failed to Download config file Ivan_Mironchuk - Adobe Experience Platform SDKs

Are you seeing any other errors past this message? is your app connecting through any sort of proxy?

Re: The best way to set up the extension "Adobe Analytics... Ivan_Mironchuk - Adobe Experience Platform SDKs

The Analytics extension for mobile allows you to configure dev, stage and prod report suites. You can also populate multiple report suites per environment by separating with a comma.

Re: Unable to create a universal framework using Adobe An... Ivan_Mironchuk - Adobe Experience Platform SDKs

@debmalya21st Are you trying to create a universal build for MacCatalyst? If so, we do not yet have support for that. Please let me know.

Re: React Native support for Campaign classic Ivan_Mironchuk - Adobe Experience Platform SDKs

@Farah-Mohammed we do not have direct react native support for Campaign Classic at this time. You could always add/initialize the Campaign Classic extensions to your native iOS and Android base project. The below screen grab would be an example of what your App Delegate file could look like in adding ACC to your base project.

Re: How to support both offline configuration & using the... Ivan_Mironchuk - Adobe Experience Platform SDKs

You would want to use this example: https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/configuration#sample-configuration to build your configuration, scraping the values from your Launch configuration: https://assets.adobedtm.com/PASTE-LAUNCH-ENVIRONMENT-ID.json These directions discuss using a bundled config: https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/configuration#using-a-bundled-file-configuration The bundled config will be used until the app gets ...

Re: Can I abort requests processing using AEP SDK and Lau... Ivan_Mironchuk - Adobe Experience Platform SDKs

Hi @Agustin_Suarez you are correct that at this time we need all the trackAction and trackState calls to exist in the app. The data elements in Launch and the rules engine operate off of data variables collected in the application. Re: your abort question, we do not have the capability to stop a call from within Launch. That is an idea we can take in for the future. Thanks!-Ivan Edited - 8/17 - We now have a new action for Mobile Core that will allow you to modify, change or remove event data fl...

Re: Equivalent to _satellite.getVar in Apps Ivan_Mironchuk - Adobe Experience Platform Launch

Hi Frederik - Can you illustrate some examples where you would set a value in Launch for a Data Element that you would want to pick up in the app? Also how often would this value change? Who is the persona that would be determining the value?

Re: Implementation of push messaging in Android Ivan_Mironchuk - Adobe Experience Platform SDKs

Hi @sinan2 - That is correct. The exact configuration necessary for receiving and displaying push messages is dependent on the steps you outlined on Firebase.

Re: Mobile Properties created in Adobe Experience Launch... Ivan_Mironchuk - Adobe Campaign Standard

Hi @vacosti - In Launch - have you:Added the Campaign Standard Extension to your property?Try only adding the server address to the Production field. Do not use the same URL address in Dev and Stage. Added the appropriate Data Elements in Launch?Published a Library that contains the extension?After that, try logging into Campaign again to see if the property shows up as "Ready to Configure" in the channels section. Users need to be part of the same Adobe ORG. Launch + ACS will not work if your C...

We want to help! Let us know if you are interested in learning opportunities. Ivan_Mironchuk - Adobe Experience Platform SDKs

We'd like to know if you would be interested in implementation-oriented learning sessions hosted by Adobe Experience Cloud mobile experts. Please fill out the quick survey below and tell us more about your interests.Adobe Experience Platform Mobile SDKs - User Feedback Survey -Ivan

Re: Adobe Experience in the Nordic markets? Ivan_Mironchuk - Adobe Experience Platform SDKs

I'm not sure which form you are referring to? Can you paste a link to the page that had the form you are looking for? This forum is the community for the Experience Platform Mobile SDKs.

Re: Migrating from Adobe Mobile SDK v4.x? Ask your migration questions here Ivan_Mironchuk - Adobe Experience Platform SDKs

Likely your v4 apps had a call similar to: ADBMobile.collectLifecycleDataThis is the same as the AEP SDK call:ACPCore.start { ACPCore.lifecycleStart(nil)}We continue to automatically collect and send lifecycle data once it is started.

Re: E/ADBMobile: AnalyticsExtension error Ivan_Mironchuk - Adobe Experience Platform Launch

This warning can be ignored. Sometimes you will see this on the initial startup as there is no shared state yet to retrieve. If you see that hits are being sent from device you are good to go!

Re: Using Adobe mobile services for mapping variables from AEP sdk Ivan_Mironchuk - Adobe Experience Platform SDKs

Hi rupaljain2408 With the latest Experience Platform SDK, the Mobile Services extension is used only for acquisition and marketing links and messaging from the Mobile Services interface. You should enable the Adobe Analytics extension to define report suites for Dev/Stage/Prod.

Re: AEP SDK for React Native - references Ivan_Mironchuk - Adobe Experience Cloud Mobile

With the 4.x SDKs you will be responsible for creating the bridging headers yourself. We do not have engineering support for React-Native with the 4.x SDKs. We are also completely ending support for the 4.x SDKs a year from now. Using the new React-Native SDKs allows for a lot of flexibility. You can use Adobe Launch for server-side configuration, which allows the customer to deploy changes on the fly. There is also the ability to use the Launch rules engine, 3rd party extensions etc.

Re: AEP SDK for React Native - references Ivan_Mironchuk - Adobe Experience Cloud Mobile

You can find iOS here: mobile-services/sdks at master · Adobe-Marketing-Cloud/mobile-services · GitHub Again, would like to caution against implementing the 4.x SDKs in a new project. You should be looking towards using the new Experience Platform Mobile SDKs. See: http://sdkdocs.com

Re: AEP SDK for React Native - references Ivan_Mironchuk - Adobe Experience Cloud Mobile

Hi puneets82097548 - The React-native versions of the SDK are fairly new. We have a number of customers that are actively working on adopting them, however we cannot release a list of references. re: SDK 4.x - Please see the latest updates on our End-of-Support schedule for v4: Version 4 Mobile SDKs end-of-support FAQ - Adobe Experience Platform Mobile SDKs Maven repo for V4 is here: Maven Repository: com.adobe.mobile » adobeMobileLibrary

Re: E/ADBMobile: AnalyticsExtension error Ivan_Mironchuk - Adobe Experience Platform Launch

Do you perhaps have batching turned on for the analytics extensio? Then hits would be queued on device. Would set batching to zero for initial development

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences