Regex POSIX char class "Print" doesn't reflect Java documentation [239189096]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

se...@gmail.com

created issue #1

Jul 18, 2022 03:41PM

https://groups.google.com/g/automate-user/c/-Tuegbe5DU8

I have only tested on a Samsung Galaxy J3 Mission (SM-J327VPP) updated to A8.1O from A7N. I can't test with newer devices

Comments

vi...@google.com <vi...@google.com> #2Jul 19, 2022 06:34AM

Assigned to vi...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build
Which Android build are you using? (e.g. PPP5.180610.010)

Device used -- Device Make, Model, Android OS Version
Apart from Samsung models, have you observed the issue on Pixel devices?

Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Screen record of the issue, if possible
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.

Capture the issue in a screenshot
Press the volume down and power buttons simultaneously. The image will appear in the picture gallery. Attach the screenshot image to this issue.

Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to android-bugreport@google.com, then share the link here.

se...@gmail.com <se...@gmail.com> #3Jul 26, 2022 11:58AM

Build: M1AJQ.J327VPPVRS3BTF2. Make: Samsung. Brand/Carrier: Verizon. Model: SM-J327VPP (one of the "SM-J327" (Galaxy J3 Mission/Eclipse) variants from different carriers. "VPP" stands for "Verizon PrePaid"). Android OS: came with 7-Nougat, and was updated via OTA to 8.1-Oreo.

I don't have access to any Google Pixel, currently.

Steps to reproduce:

Install Llamalab Automate
Download this "flow" script
Import the flow into the app by clicking the 3 dots in the corner
Open the flow and start it
Type any printable Unicode character not in 7bit-ASCII range (BMP also counts), like an emoji or a Greek char
A message will be shown with the truth values of the regex match: The current behavior is that "POSIX" section says "Yes", while "char class" section says "No". The expected behavior is that both should say the same thing (regardless of input text), in this case "No"

I'll add some screenshots later

su...@google.com <su...@google.com> #4Jul 27, 2022 07:00AM

Could you please share the screen record followed the steps mentioned in comment #2.

se...@gmail.com <se...@gmail.com> #5Jul 28, 2022 12:13AM

Yes, I'm going to record right now. I also found out that the same issue happens in QuickEdit, but not in Acode. Acode is the only one that's open-source, I'll later search for a FOSS app with the same issue. It seems both AM and QE use the built-in regex engine, while Acode uses a 3rd party

se...@gmail.com <se...@gmail.com> #6Jul 28, 2022 12:37AM

I forgot to say that Acode doesn't recognize any kind of POSIX char classes. Here are the links to the videos: Automate QuickEdit

vi...@google.com <vi...@google.com> #7
Restricted
Jul 28, 2022 10:44PM

Comment has been deleted.

vi...@google.com <vi...@google.com> #8Jul 28, 2022 11:27PM

Thanks for the above inputs, please share the bugreport as requested in

comment#2

. Also kindly confirm the issue is reproducible on the latest Android versions.

se...@gmail.com <se...@gmail.com> #9Jul 29, 2022 12:33PM

Ok, I'm now going to capture the bug report. My bootloader is completely locked by Verizon, I can't install a recent GSI, and I don't have access to any new Android version (I'll need to ask some contacts to test the bug for me)

se...@gmail.com <se...@gmail.com> #10Jul 29, 2022 01:27PM

Comment has been deleted.

Message last modified on Jul 29, 2022 06:35PM

se...@gmail.com <se...@gmail.com> #11Jul 29, 2022 01:28PM

I also sent the report link to android-bugreport@google.com

se...@gmail.com <se...@gmail.com> #12Jul 29, 2022 06:36PM

I deleted it, because I noticed it contains "sensitive info". I thought it would only include activity at the moment of capture, but it also includes logs of old things. Is there a way to send a report with less data?

se...@gmail.com <se...@gmail.com> #13Jul 31, 2022 03:58AM

Wait, why do I have to send a bug report in the first place? And if it contains "sensitive data", why did you suggest me to post the link publicly? Isn't sharing the folder with Google already enough?

vi...@google.com <vi...@google.com> #14Aug 1, 2022 07:52PM

We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

vi...@google.com <vi...@google.com> #15Sep 16, 2022 12:30AM

Marked as fixed.

Our development team has fixed the issue you have reported and the fix will be available in future Android release.

se...@gmail.com <se...@gmail.com> #16Oct 1, 2022 04:26PM

Thank you

se...@gmail.com <se...@gmail.com> #17Sep 26, 2023 03:29AM

The issue persists on Samsung Galaxy A31, SM-A315G, OS 12.0

Was this fixed in Android 13 or 14? I can't use a VM right now