Not sure where you got 50MB from, but that is incorrect.
With the latest release (6.3.4) the SDK will add a little less than 1MB to your application.
If you would like to verify this you can use our LearningApp (https://github.com/salesforce-marketingcloud/MarketingCloudSDK-Android). The built APK with minification disabled is only 4.9MB. With ...
For most devices, removing the app from recents will have no effect on whether the app can receive a push message. For some device models, I have seen that removing an app from recents is treated the same as force stopping the app. This is an attempt by the manufacturer to gain better performance, usually as related to battery, on a low-end device. This ...
This is covered in the github 'Registration Updates Via Contact Key, Attributes, and Tags'
The SDK will send changes to the Marketing Cloud servers within one minute of the first change to any Marketing Cloud Mobile Push device or contact registration record and no more frequently than once per minute after as required. This can be data set by your ...
You don't have to do any changes in SDK. All you will be configuring auth keys in Marketing Cloud UI instead of certificates.
Using the steps in the same URL which you have provided in your question - https://org62.my.salesforce.com/sfc/p/#000000000062/a/0M000000OMhD/Ssu9rGuCZ7kc1aAvxGmqQGIhEK_hPvOxALWwdB9D1CE, change certificate to auth keys.
So, you can ...
Please see https://salesforce-marketingcloud.github.io/MarketingCloudSDK-iOS/sdk-implementation/user-data.html#reserved-words. You should not be setting this value manually.
Also, if you're having issues with the opted-in status of a device or devices then you should verify the APNS certificate you have registered with the Marketing Cloud servers. The ...
If I understand the question correctly, you're attempting to:
- Limit the lifespan for viewership of an in-app message for 7 days based on the messages arrival time on the device.
This is not currently supported by the Marketing Clouds MobilePush In-App Message platform. It is however, a unique and very interesting use case. My recommendation at this point ...
99.999% of the time this is simply a certificate issue. Please verify that you've uploaded the correct certificate to the Marketing Cloud Servers. If you need further assistance please open a support case through your support representative.
Capacitor is not a platform we officially support, but I do know that customers are using it and we have not heard about any large blocking issues. Our upkeep of Cordova is minimal at this point but we do not have any plans to adopt Capacitor at this time.
PWA Apps are basically Websites running on modern browsers. Push notifications in PWAs context are simply Browser notifications and for the moment MobilePush doesn't support Web notifications.
The MobilePush SDK only supports :
iOS native code -> https://salesforce-marketingcloud.github.io/MarketingCloudSDK-iOS/
Android native code -> https://salesforce-...
The application should be careful not to hold on to instances of smartstore or mobile sync manager after a logout. The fact it works on restart means it is probably what is going on. One way to achieve that is to avoid capturing the sync manager or smartstore in a instance variable and instead use a helper method like the following:
func getSmartStore() -&...
Please see Google's LONG STANDING bugs with regards to JobIntentService and "star" this bug (ref. https://issuetracker.google.com/issues/63622293) and the other similar associated bugs. This bug is not being generated by the Marketing Cloud SDK.
I would recommend using LanguageLocaleKey and LocaleSidKey fields from a context User. Based on that you can set specific locales on mobile before displaying the data.
From User | SOAP API Developer Guide:
Required. This field is a restricted picklist field. The value of the
field affects formatting and parsing of values, especially ...
Only the mobile browsing experience is being removed. The standard app as well as any custom apps won't be affected by this feature being removed, as they do not use the mobile web experience (found by going to https://login.salesforce.com/ on your phone in Google Chrome, Safari, etc).
I don't know about "system" personalization strings, but if you send your inbox message from Journey Builder, all the data from your entry source can be used in the CloudPage (source : https://help.salesforce.com/articleView?id=mc_rn_april_2019_mp_jb_entry_source_personalization.htm&type=5). I tested it a few months ago (with a Data Extension entry ...
@jclobro, are you validating the result returned from your call to sfmc_setAttributeNamed()?
The method will be returning false in your example, and if you have debug logging enabled in the SDK you'd see:
[foundation] sfmc_setAttributeNamed key: OptInStatusID, value: ??? failed, name is not valid
Additionally, if you pass an empty string ( "" ) you'll see:...
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.
As of today Lighting Components are not supported in the Mobile SDK. I have not heard about Lighting Components not rendering properly, the issues we have encountered have been about long term session management and navigation. If your app is a simple, single page full screen web experience you may be able to simply wrap the LC in VF, though I wouldn't ...
Can we expect the Salesforce Mobile SDK to support a fairly recent version of React Native anytime soon?
We don't know. Until/unless we see something in the release notes, we can make no assumptions about supporting a newer React version. You might ask this question of salesforce.com directly, but Support probably doesn't know any more than we do.
The way I've generally solved this is to retrieve your Lead ID/Contact ID at the time of login in your mobile app.
You could either
1) During authentication, if there is a successful login your authentication API could be modified to return the Salesforce Contact/Lead ID.
2) After successful authentication, make an API call to Salesforce CRM to lookup the ...
Go to Setup>>Connected Apps>>Salesforce CLI>>Edit Policies>>IP Relaxation>>Relax IP restrictions.
This worked for me.
Other workarounds to try are:
Log out completely from browser and try again.
Clear Cache and try again.