Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In App messages doesn't unfocus input #176

Closed
beqramo opened this issue Jul 24, 2023 · 6 comments · Fixed by #350
Closed

In App messages doesn't unfocus input #176

beqramo opened this issue Jul 24, 2023 · 6 comments · Fixed by #350

Comments

@beqramo
Copy link

beqramo commented Jul 24, 2023

Hi,

When in app message is sent, library don't remove the keyboard, because of that it looks terrible.
This needs to be fixed from the library level.

@mrehan27
Copy link
Contributor

Thank you for reaching out to us. Could you kindly provide more details about the issue?

  1. Are you expecting the keyboard to be automatically closed in the background when the in-app message is received?
  2. Please specify the platform (iOS or Android) on which this issue is occurring.
  3. If possible, sharing a screenshot would greatly assist us in understanding the problem.

@beqramo
Copy link
Author

beqramo commented Jul 24, 2023

  1. yes. because you can't overlay on the keyboard and when it is a modal like in app message it looks ugly.
  2. it was seen on ios i haven't test on android but if there is no logic it will be same.
  3. I can't find it now, but the situation was like this: I'm showing the input with a keyboard and at that time we are triggering in app is visible on top of the viewable area but the keyboard isn't visible still. so it doesn't make sense to have the keyboard opened

@mrehan27
Copy link
Contributor

I tested this, and the issue doesn't occur on Android. However, I was able to reproduce the issue on iOS. I have created an internal ticket and added a vote on your behalf to prioritize its resolution. We will keep you informed of any updates or when the issue is fixed.

Thank you for sharing. Have a great day.

@beqramo
Copy link
Author

beqramo commented Oct 25, 2023

any update?

@lj-cio
Copy link
Collaborator

lj-cio commented Oct 25, 2023

Hi @beqramo, thanks for your patience here and for the reminder. The issue that @mrehan27 created on your behalf has been scoped and we're optimistic about an approach to fix the issue, but have so far prioritized in-app and SDK improvements that have pushed the changes needed here further out.

If our priorities seem wrong or we're missing additional context, would you be open to a quick call to better understand your use case and how your app and flows are impacted?

@ami-aman
Copy link
Collaborator

Hi @beqramo

Good news! The fix for this issue is now available in version 4.0.2. This version of customerio-reactnative also includes support for CDP (Customer.io Data Pipelines). If you haven’t upgraded to version 4.x yet, please refer to our migration guide and quick start guide for assistance.

With the release of this fix, we’re closing this issue. However, feel free to open a new issue if you have any questions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants