4
If you have more than 1 service declared in your application then there's a Google bug in their GcmReceiver which may be getting in your way. See https://salesforce.stackexchange.com/a/128740/16482 for details, but net-net-net, manually declare the ETPushReceiver in your manifest and ensure that it is the 1st service listed.
3
This is basically because how Salesforce1 is implemented on Android. The main UI is provided by the OS (a WebView component), so when you navigate to a normal URL in an app that is outside of Salesforce1's registered URL handlers, it will be routed to the default browser. You'll need to instead use an XMLHttpRequest to simulate the form submit, and depending ...
2
It looks like you're trying to replicate the standard Salesforce functionality. Take a look at this article:
https://help.salesforce.com/articleView?id=000230821&type=1
In a few words, you can give access to a connected app via permission set to specific users. From the question description, it looks like this is what you actually need.
Also, you can ...
2
Two things are at play here.
First off, the fact that your title is arriving on the device with the apostrophe escaped is a bug in the Marketing Cloud UI that has been fixed, but not released.
Second thing is with regards to the Notification.Builder. The reason you're not seeing the title change when you use the setContentTitle method on the builder is ...
2
Unfortunately there is no workaround for this issue, however it has been corrected in version 5.3.x of the SDK.
The current release, as of 20171214, is v5.3.2.
2
There is not.
Prior to version 4.9.x the Android SDK hashed together some bits of data and ANDROID_ID in order to generate it's unique device identifier. At the time this decision was made, 2011/2012, this was considered safe and resulted in a repeatable, unique device identifier.
Since then, however, several device manufacturers and 3rd party ROM makers ...
2
Same steps worked well for me and I see the login screen when I launch the app. I see the following error in your log
The node package shelljs is required to use this script. Run 'npm install shelljs' before running this script.
/Users/itsme/projects/myApp
Update - I see this issue was logged on the Mobile SDK repo and has been closed as an environmental ...
2
Either remove the duplicated dependencies from your application or exclude them from the SDK using Gradle's implementation ('mc sdk') { exclude ... } syntax.
2
MarketingCloud Mobile Push SDK v8.0.0 has been released. This release includes support for Android 12.
2
You can switch to a different business unit be simply calling the MarketingCloudSdk's init method with the credentials of the new business unit. This will signal to the SDK to clean up the existing configuration and re-initialize with the new configuration.
There is no guarantee that the device will not still receive push messages from the previous ...
1
This problem is not related to Marketing Cloud SDK at all. Just creating my own notification I can replicate the problem, so the fix was to add Intent.FLAG_ACTIVITY_CLEAR_TASK | Intent.FLAG_ACTIVITY_NEW_TASK to my landing ResolverActivity.class Intent. You can also add Intent.FLAG_ACTIVITY_REORDER_TO_FRONT instead of Intent.FLAG_ACTIVITY_CLEAR_TASK and it ...
1
I suspect you're not initializing the SDK in your application's onCreate() method and/or you're delaying/preventing the SDK from being initialized.
Also, if you're application is calling getInstance() I would suggest refactoring it to use requestSdk().
@Nullable @MCKeep public static MarketingCloudSdk getInstance() {
if (!isInitializing && !...
1
SalesForce has released a new version of the SDK that addresses this issue:
SDK v224.1.2 (Chat v4.2.2)
Fix: Allows customers to upgrade their targetVersion to API 31 (Android 12). Without these changes, customers would get build issues or crashes on Android 12 if their app targeted API 31 (Android 12).
implementation "com.salesforce.service:chat-ui::4....
1
According to the SDKState output you have multiple FCM messaging service classes registered in your manifest at a higher priority than the one used by the SDK. com.example.login.service.MyFirebaseMessagingService and io.smooch.core.FcmService.
If this is intentional then you need to follow the instructions for implementing multiple push providers in your ...
1
The Attributes can be set with firstname and lastname without spaces. This can be seen in the MobilePush Demographics under Audience Builder. This has always been the case, but I do not know why.
1
Salesforce SDK for Android seems to use an earlier version of opentok-android-sdk (2.16.3), which has dependency on opentok-android-sdk-v3-3.1.3, which seems to be no longer available (see https://support.tokbox.com/hc/en-us/articles/360059402811-Android-SDK-available-through-maven-central).
The best way to get over this issue would be for Salesforce to ...
1
The LWC OSS Scaffolding or Project Builder has a PWA (Progressive web app) option. This option allows you to build a "regular web app" which can be "downloaded" to users devices as if they were native to the device. So, you can skip the overall SDK and focus on building an app that will be supported on any device. For more on Progressive ...
1
The issue was I implemented the notification handler, FirebaseMessagingService. So I had to implement the MarketingCloud handler within onMessageReceived
if(PushMessageManager.isMarketingCloudPush(remoteMessage)) {
MarketingCloudSdk.requestSdk( sdk -> {
sdk.getPushMessageManager().handleMessage(remoteMessage);
});
}
as ...
1
If you have implemented our SDK alongside another push provider, to include Firebase's own messaging service, then you must get and handle the token yourself. An example of this can be seen in our "learning application" (ref. https://github.com/salesforce-marketingcloud/MarketingCloudSDK-Android/blob/master/app/src/mpp/java/com/salesforce/marketingcloud/...
1
You should be using version 17.0.1 of firebase-core.
The SDK docs page uses a shared variable for the Firebase major version number, which is no longer correct since Google is publishing no longer publishing the same major version update for all Firebase libraries at the same time.
The docs will be updated shortly to reflect the correct version.
1
This has been resolved as of version 4.7.x of the SDK: Release Notes
Please update to the latest version and, as always, please let us know if you're experiencing any issues.
1
I get the same issue, you can fix the build by having
android {
testOptions{
unitTests.all {
jvmArgs '-noverify'
}
}
}
in your build.gradle file, or if you're running from Android Studio/etc put '-noverify' in your VM Args for the run config
unfortunately after solving this issue I then get the following when ...
1
Salesforce Mobile SDK v3 is available and it solves this problem. You need to upgrade forcedroid and other mobile sdk stuff via NPM to get that.
As shown in picture below, the login window now always shows the action bar and easy way to change server.
But ran into other issue, after upgrade on existing projects i.e.
"Uncaught module com.salesforce.plugin....
Only top voted, non community-wiki answers of a minimum length are eligible