For some reason, I keep getting "Invalid installation url" error when I try to change URL to a self hosted Linux chatwoot app that was setup on a new Ubunutu 20.04 system using the installation script at https://raw.githubusercontent.com/chatwoot/chatwoot/develop/deployment/setup_20.04.sh.

The installation has no issues as I am able to login to the web interface just fine using the default [email protected] account. Tried the app on two separate Android devices and both have the same error message when trying to change the URL.

The default app.chatwoot.com URL works fine but would like to use the app on our self hosted install.

Any ideas how to debug? The error message should have more details added in a future app versoin to let us know exactly why the installation url is invalid.

I'm getting the following error.

`FAILURE: Build failed with an exception.

 What went wrong:
Execution failed for task ':posthog-react-native:generateDebugRFile'.
This project uses AndroidX dependencies, but the 'android.useAndroidX' property is not enabled. Set this property to true in the gradle.properties file and retry.
`

I've followed all the instructions in the guide. AndroidX is enabled in gradle.properties Maybe it's related to a new third-party library which was added recently. My environment - Mac OS Big Sur. Tried even on windows 10 but got the same exact error.

Confirm you’re filing a new issue. Search issues in Github and ensure that the issue is not already exist.

Checked

Describe the bug

Sending a message on Android app shows "Could not connect" message, even though it works, the message is delivered

To Reproduce

See notification of a new message received Open Chatwoot mobile app Reply See message

Screenshots

Observed behavior Environment

• Describe whether you are using Chatwoot Cloud - yes
• Device Name: Xiaomi Mi 11 5G
• OS Version: Android 11
• Chatwoot App Version: latest from app store
  • Chatwoot Server Version: hosted by you

@muhsin-k here is pull requests for #30 PR contain setup for iOS with single simple tests. There are some issues about PR:

• [ ] tests are not included in CI.
• [x] which ios configuration should be tested: debug or release? Now is debug, it is discussable.
• [ ] I haven't test with android, should I?
• [x] e2e dir excluded from eslint check. Looks like not OK, and should be fixed. What do you thing?
• [x] simulator should be run before run tests. It is looks like bug, I am researching.

Any feedback is welcome.

Android app v.1.4.5 Every time I open the app, it asks me for the installation URL, username and password. Looks like the session does not last. The previous version was not doing it.

In the latest stable version of React Navigation i.e 5.x if some data is being fetched from any API the navigations calls won't go through. This causes the chatwoot-mobile-app to lag and as the scene doesn’t change as expected the parts of the app such as opening a conversation from the flatlist feels irresponsive because the navigation call doesn’t go through instantaneously because some data say user avatar image is being fetched while it was tapped. Maybe wix/react-native-navigation can be looked at instead of react-navigation as it's a native implementation. This is also evident in the Bottom Tabs. On iOS navigation is fast and as expected but on Android, this is a problem even on a decent device.

Some issues created in the official react-navigation repo for reference:

https://github.com/react-navigation/react-navigation/issues/8269

https://github.com/react-navigation/react-navigation/issues/5990

• Replaces direct theme references with one provided by context (ApplicationProvider). Now this app can be easily integrated with both light and dark themes.

• Replace redundant styles and theme variables by modifying the original variables.

• Improve text styling by moving the code for determining fontFamily to custom mapping.

• Improve performance by build-time processing of mapping (don't rename mapping.json into .js as it will break build-time processing)

Notes

You may slightly improve your UX if you combine the typography variables into a single instances defined in mapping.json. I did this for fontWeight and fontFamily properties. You can also bring additional consistency into this by adding fontSize as well.

Also, you may reduce usage of custom theme variables like background-*** by using of the original background-basic-color-*** variables. In Eva, this colors are used as backgrounds and if you start using custom ones, it makes sense to see this guide on modifying them.

General advices

To access current theme within class components, you may use withStyles + this.props.themedStyle to access styles you create.

In function components, you may do this with StyleService.create + useStyleSheet.

I suggest using one of them by refactoring existing code base into classes or functions and not mixing these patterns to make your code look consistent.

Instead of using borderBottomColor + borderWidth: 1, you may use Divider component that is exported from UI Kitten.

Pull Request Template

Description

Added the support for sending an email with mentioned CC and BCC email addresses.

Fixes #511

Type of change

• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Screenshot

Checklist:

• [x] I have performed a self-review of my own code
• [ ] I have commented on my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have tested in both Android and iOS platform
• [x] My changes generate no new warnings
• [ ] Any dependent changes have been merged and published in downstream modules

Pull Request Template

Description

!. Add the ability to mute and unmute the conversations. 2. Improved UX for resolving and reopening conversations.

Fixes https://github.com/chatwoot/chatwoot-mobile-app/issues/295 https://github.com/chatwoot/chatwoot-mobile-app/issues/477

Type of change

• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Screencast

https://user-images.githubusercontent.com/64252451/168246814-67ccec1b-ddff-472b-ae23-5d8f45316eb4.mov

Checklist:

• [x] I have performed a self-review of my own code
• [ ] I have commented on my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have tested in both Android and iOS platform
• [x] My changes generate no new warnings
• [ ] Any dependent changes have been merged and published in downstream modules

To Reproduce

Type anything ending in .delivery example: myapp.delivery

Expected behavior

The .delivery TLDs are valid, so the application should accept them.

Observed behavior

I created a subdomain in a .com TLD to temporarily solve the problem and it worked.

Environment

• Self hosted.
• Device Name: Android
• OS Version: 12
• Chatwoot App Version: 1.4.3
• Chatwoot Server Version: 2.4.1

Possible fixes

Allow domains ending in .delivery in the application.

It's showing "not identifiable by github", dont know if it's the badge provider error or something else, instead this below one can be used or Shields.io has autogenerated license badges: https://img.shields.io/github/license/chatwoot/chatwoot-mobile-app

Describe the bug

We've been using Chatwoot for a bout a year. The iOS app has been working smoothly most of the time. However since about 1 month it is unbearably slow to interact with. Pressing a button makes the action happen 10-15 seconds later (if at all). The chat submit button does not send the message at all even if the UI shows that the action is received.

To Reproduce

Hard to tell

Expected behavior

A quick and responsive UI

Environment

• Self hosted
• Device Name: iPhone12
• OS Version: 16.1.2
• Chatwoot App Version: 1.6.18
• Chatwoot Server Version: 2.9

Is your feature request related to a problem? Please describe. When phone is connected to Android Auto, the smartphone don't receive notifications on Android Auto system and it's shown only on phone screen without audio notifiy. Would be wonderful to receive notification on Android Auto notifications system.

Describe the solution you'd like When receive a notify from App when connected to Android Auto receive notifications on Android Auto Notification System.

Bumps decode-uri-component from 0.2.0 to 0.2.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Images sent or received are not shown on the Android Client.

A clear and concise description of what the bug is.

I am unable to see chat images sent or received using the Android Client.

How can we reproduce the issue

• Open a Conversation in the computer browser
• Send or receive a image in the chat
• Open the same conversation in the Android app and try to see the image - the image will not be shown, as seen below:

Expected behavior

Images should be shown the same way they are shown in the browser.

Screenshots

Environment

• Hosted Installation (Docker - latest version)
• OnePlus 6
• OS Version: 10.3.11
• Chatwoot App Version: 1.6.18
• Chatwoot Server Version: 2.11.0

UPDATE 10.11.2022 the problem with the offline / online situation was fixed by setting the working ours. BUT: the assignment doesn't work, like I described it below (case 2)

UPDATE 09.11.2022 in the second video the widget jumps to offline (from second 9), although I am online in the ios app. Yes - this is the real problem. As you can see, while my ios app is permantly active, the widget switches from offline to online to offline, etc...

https://user-images.githubusercontent.com/17011498/200797208-89846a09-b1df-4dad-8e3d-ece52696234d.mp4 https://user-images.githubusercontent.com/17011498/200797250-9c2965ed-29d2-43ee-89f3-9bc3c869a3f8.mp4

Hi all!

I have found a bug which should be fixed as soon as possible. Version: Self hosted (docker)

Case 1

• I am logged on to the PC as agent (web interface)
• User writes a message via Widget
• Dialogflow responds with a custom payload: { "action": "handoff" }
• User is assigned to me

Result: OK

https://user-images.githubusercontent.com/17011498/200773572-c79975e3-fb2f-45e0-9183-ae2a120d4b6a.mp4

Case 2

• I am NOT logged on to the PC as agent (web interface) (only on ios app)
• User writes a message via Widget
• Dialogflow responds with a custom payload: { "action": "handoff" }
• User is NOT assigned to me - no assignment!!

Result: NOT OK

https://user-images.githubusercontent.com/17011498/200774004-758d2bac-c981-456b-bf8d-da55bff77450.mp4