Hi @Leina_Betzer - There are a couple of ways to do this: You can check
your pod file or your gradle.build settings to see the versions fetched
for iOS or Android. You can use APIs to get extension version
information ->
https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/signals/signal-api-reference#version-of-the-signal-extension
(This is an example for the Signal extension, but is something that can
be done with each extension)Preferred method - Use Project Griffon's
Extensio...
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
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...
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.
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.
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.
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
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...
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...
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...
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.
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.
@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.
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 ...
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...
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?
Hi @sinan2 - That is correct. The exact configuration necessary for
receiving and displaying push messages is dependent on the steps you
outlined on Firebase.
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'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
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.
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.
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!
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.
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.
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
