Hey @det2020 -Most of the time a user's selection on OS prompts like
requesting for permission will result in a call to a delegate method
that the developer controls. In the case of location permission, the
CLLocationManagerDelegate will be notified via the
locationManagerDidChangeAuthorization: method.In a delegate method like
that, you can invoke any AEP Mobile SDK method you'd like.Hope this
helps!-steveb
Hey John, Sorry about the confusion, looks like we haven't updated the
documentation at the second link you provided. We will make sure to get
that updated! The AEP SDK does support Cordova. Please see the GitHub
repo for more information: https://github.com/adobe/cordova-acpcore Hope
this helps. -steveb
Hey @jorisdebeer,Great question! Hopefully I can clear things up by
providing a little insight on when First Launches and Upgrades are
reported.First Launches - this event is only sent in the first time a
user launches your app. Think of a first launch as a net-new
user.Upgrades - this event is only sent in the first time a user
launches your app, and the previous launch of your app was a different
version.These are both event-type variables, meaning they get counted
only when they're sent in. I...
Hey rupaljain2408 - Assuming you're using the same Analytics
configuration (report suites and data collection server) for both your
v4 and AEP SDK implementation, this shouldn't be a problem for you. Hope
this helps.steve benedicksr mobile software engineerAdobe Experience
Cloud
Hey Stephen,Glad to hear you've got things running!Regarding product
string, the suggested implementation is outside of context data. There
is a special combination of characters that you can use in your context
data key to indicate you want a value to go directly in the hit instead
of being a part of context data, outlined more for you here: Product
variable - Adobe Experience Platform Mobile SDKsHope this helps.-steveb
Yeah, sounds like you're familiar with the v4 SDK where all lifecycle
traffic was handled automatically in iOS . In the new SDK, it's now a
manual process, which provides more flexibility for our customers. Read
here for more info on lifecycle: Initialize the SDK and set up tracking
- Adobe Experience Platform Mobile SDKs Hope this helps.-steveb
Hey dbtrade,I have been unsuccessful in trying to reproduce this issue.
Would you mind sharing more information about your environment? What
version of Xcode are you using?Is this a Swift or Obj-c app?Looks like
you're using the Cocoapod, can you confirm? If so, would you mind
sharing your Podfile?What settings are you enabling when building your
Ad Hoc distribution?Thanks.Steve BenedickSr. Mobile EngineerAdobe
Experience Cloud
Hey James,Thanks for the feedback on how we can improve our docs.
Hopefully we can make some improvements there to make this less
confusing.From a high level, you can think about the data collected from
your marketing links in two categories: acquisition, and re-engagement
(deeplinks). If your link is for acquisition purposes, the data will be
stored in an non-expiring eVar. If your link is for re-engagement
purposes, the data will be stored in a eVar that is only valid per
visit. In either case...
Hey Jay,I believe you will need two separate login companies to
accomplish what you're after. You can delegate your apps into each login
company, and have the group of admin users be different for each
company. I'd recommend contacting your Analytics consultant to see if
they can help you get your configuration set up properly. Hope this
helps.steve benedicksr mobile software engineerAdobe Marketing Cloud
"Launches" is measured client-side. A launch event will only occur if
the user actually opens your app (bringing it to the
foreground)."Visits" is measured server-side (based on an activity
timeout). By default, a new visit will be reported when a hit comes in
from a user and that user has not sent in a hit within the past 30
minutes.The most common cause of having more UVs than launches is when a
mobile app is doing tracking from the background. In this case, a new
visit can be created without ...
Hey Jeff,As mentioned earlier in this thread, there is a way to send
data to multiple report suites with a single request. However, there is
no API in the mobile SDK to dynamically add and/or remove report suites
at runtime, which means that all of the report suites you list in the
ADBMobileConfig.json file will get data for every request. You can
achieve what you want by implementing Vista rules. With Vista rules, you
can decide which report suites should process each request based on the
conte...
In an earlier post in this thread (that post appears to have been
deleted?), it was stated that the Visitor ID was partially generated
using information specific to the device. I simply wanted to clarify
that device information is not a part of the process used to generate a
Visitor ID. -steveb
@Adrian, @Tanmay - It is accurate that a delete and reinstall of the app
will cause a new visitor to be generated. I need to clarify that while
clearing app cache will not cause a new Visitor ID to be created,
clearing app data will result in a new Visitor ID being created. Also
worth noting that the SDK uses no information about the device when
generating the Visitor ID.Sorry for the confusion. Hope this helps.
steve benedicksr mobile software engineerAdobe Marketing Cloud
Hey Anudeep,At its core, Bloodhound is just a proxy server. If the IP
address of Bloodhound is used as your endpoint for your request
(192.168.0.100:50000 in your ADBMobileConfig.json attached), the concept
of forwarding is lost - there is nowhere for Bloodhound to "forward" the
hit to.Instead, you should use your Analytics tracking server in the
config file (as mentioned by JillsMatthew above). You should then modify
the network settings on your test device to proxy via Bloodhound. You
can do t...
Hey Anudeep Srivastav ,It looks like your device/emulator isn't able to
communicate with your Bloodhound instance. I would double-check your
ADBMobileConfig.json file to verify it's pointing at the IP Address of
your Bloodhound proxy. Hope this helps.steve benedicksr mobile software
engineerAdobe Marketing Cloud
Hey Gary,Can you please post the debug log here?A couple of things you
can check: Have you connected your device to a proxy to see if hits are
leaving the device? Have you tried sending in any other data to your
report suite from your UWP app? Thanks!steve benedicksr mobile software
engineerAdobe Marketing Cloud
Hey there, The CrashEvent is set on launch when the Adobe SDK is not
aware that the app exited/closed correctly in its previous run. In
Windows, you have to tell the Adobe SDK when the app is suspended or
closed. Please verify you have correctly implemented lifecycle by
referencing the section called "Lifecycle Metrics" on this page:
https://marketing.adobe.com/resources/help/en_US/mobile/uwp/analytics.html
Hope this helps. -steveb
Hello,This exception is most commonly caused by our library when the
Windows C++ Runtime Library can't be found. Please ensure your Windows
Phone project includes a reference to "Microsoft Visual C++ 2013 Runtime
Package for Windows Phone". If it already has this reference and you are
still having an issue, please reach out to client care as suggest by
Shekhar above. Hope this helps. Steve BenedickMobile Software
EngineerAdobe Marketing Cloud
Hey Merve, I won't provide any specific Android code, but I will give
you this link which provides you all you need to know about the Android
push message payload:
https://developer.android.com/google/gcm/adv.html#payload Note the 4k
limit. You likely won't run into the size limit, but the process is
largely the same. Make sure you put a variable in the payload of your
push message, then handle it as desired in your Android activity. Hope
this helps. steve benedickmobile software engineerAdobe M...
Hey Sparro, We'd be happy to take a look at your issue, but we'll need
information that you probably don't want to share in the forums 🙂
Please log an issue with client care and we will get it fixed. Thanks!
steve benedickmobile software engineerAdobe Marketing Cloud
Greetings, In Adobe Analytics, by default, enabling Mobile App Lifecycle
Reports will automatically update your navigation menu. However, if you
are using a custom menu, it is likely you will need to go add the
reports you're interested in to your white list of reports. As mentioned
by Alexis, Adobe Mobile Services is a nice way to get at all your mobile
data. I would recommend checking it out. steve benedickmobile software
engineerAdobe Marketing Cloud
Hey Mike, Sending hits when the app enters the background (or while the
app is in the background) can cause issues in your lifecycle data. If
you are sending hits via the SDK from the background, make sure you're
using the trackActionFromBackground:data: message. Using this will
suppress new lifecycle sessions from being created by your app's
activity while it's in the background.If this doesn't help, I recommend
contacting Client Care so we can get a ticket open for you. steve
benedickmobile so...
First I'll tackle how we track crashing. As the documentation states,
when the app doesn't "exit gracefully", we send a crash on the next
launch. By exiting gracefully, all we mean is entering the backgrounded
state (receiving the applicationDidEnterBackground notification from the
OS) prior to the app closing. Any time the user pushes the home button
on their iOS device, the current app will be backgrounded (this includes
pressing the button twice to pull up the app switcher for multitasking
pu...
Hey Lucia,We haven't released any updates to BH since late last year, so
from a technical side, I'm not sure I can offer much advise as to why
Bloodhound (or any other proxy tool) would have stopped working for you
in April. The first thing that I do when diagnosing issues with
Bloodhound is make sure that I can see the server from my web browser.
If your Bloodhound instance and device are on the same subnet, entering
the ip/port combination into the browser on your device should take you
to a "...
Hey Florian, We spent a little more time looking into this issue today,
and unfortunately there is nothing in the information that we have that
can give us a good lead as to what's happening (whether in our SDK or
not). We know there is an SQLiteStatement.execute() method called from
our SDK, and that it is properly handled in try/catch blocks. We can't
say for sure if control is ever passed back to the SDK based off the
stack trace. What we need at this point is more information. If you have
a ...
Hey Florian, I took a look at the stack trace you posted, and it looks
like there is a recursive lock in sqlite. You'll notice that the
following 5 lines in the stack trace are repeating:at
android.database.DefaultDatabaseErrorHandler.onCorruption(DefaultDatabaseErrorHandler.java:81)
315 at
android.database.sqlite.SQLiteDatabase.onCorruption(SQLiteDatabase.java:338)
316 at
android.database.sqlite.SQLiteProgram.onCorruption(SQLiteProgram.java:111)
317 at
android.database.sqlite.SQLiteStatement.si...
Hey Peter,The current SDK for Windows 8.1 Universal Applications is
written in c++, and requires that you select your architecture at build
time. "Any CPU" is not supported.A Windows 10 SDK is on the roadmap, but
we do not have a date to commit to at this time. Thanks! steve
benedickmobile software engineerAdobe Marketing Cloud
