You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.
Describe the issue
I was installing Android and there are some steps that didn't work for me. For example I was able to make it work like this:
On the step 3 of Android installation instead of implementation project(path: ':@loadsmart_rn-salesforce-chat') I changed to implementation project(':loadsmart_rn-salesforce-chat')
For the step 4 I didn't have to add the new RNSalesforceChatPackage() to the getPackages it gives me an error after a success build complaining about this because it was already added maybe because this is part of the manual installation
The rest of the steps worked perfectly as the docs explained on Android and I was able to use the chat with salesforce
For IOS it give me and error at the beginning about setting the minimum deployment target to low: (I had 11 and the library required 12), I changed that and it worked perfectly also. I was wondering if there is something we can do to avoid setting this minimum deployment target to 12? since a lot of my customers are using IOS 11 I was hopping not to set this restriction in order to use this library since is the only one that worked for the salesforce chat. Is there a way to set this deployment lower in the library? it's possible? Thanks in advance!
NOTE: Please let me know if this changes in the setup process for Android are ok and I will be happy to create a PR to update the docs.
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
rn-salesforce-chat version (please complete the following information):
Version: 3.2.0
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
MarlonAEC
changed the title
[🐛] Bug/Issue Report Title - Not a bug but some clarifications about setup
[🐛] Not a bug but some clarifications about setup
Jan 2, 2023
Describe the issue
I was installing Android and there are some steps that didn't work for me. For example I was able to make it work like this:
implementation project(path: ':@loadsmart_rn-salesforce-chat')
I changed toimplementation project(':loadsmart_rn-salesforce-chat')
new RNSalesforceChatPackage()
to thegetPackages
it gives me an error after a success build complaining about this because it was already added maybe because this is part of the manual installationThe rest of the steps worked perfectly as the docs explained on Android and I was able to use the chat with salesforce
For IOS it give me and error at the beginning about setting the minimum deployment target to low: (I had 11 and the library required 12), I changed that and it worked perfectly also. I was wondering if there is something we can do to avoid setting this minimum deployment target to 12? since a lot of my customers are using IOS 11 I was hopping not to set this restriction in order to use this library since is the only one that worked for the salesforce chat. Is there a way to set this deployment lower in the library? it's possible? Thanks in advance!
NOTE: Please let me know if this changes in the setup process for Android are ok and I will be happy to create a PR to update the docs.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Smartphone (please complete the following information):
rn-salesforce-chat version (please complete the following information):
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: