IssueTracker

Hello,

We have shared this to our engineering team and unfortunately I am not able to provide an E.T.A on the fix. Future update(s) will be posted here.

We recently implemented an experimental workaround for this. We're looking for feedback on it if you'd like to give it a try. What you'd need to do is one of the following:

1. Add an iframe in your application pointing to /_gcp_iap/session_refresher, e.g. <iframe src="/_gcp_iap/session_refresher" style="width:0;height:0;border:0; border:none;"></iframe>

2. Instruct your users to load https://yourapp/_gcp_iap/session_refresher in an extra tab.

I realize this is hoaky and no substitute for a proper fix, but let me know if it's at all a viable workaround for you!
  --Matthew, Cloud IAP engineering lead

Appears to work. Thanks

@ms...@google.com We're using the second option you listed now and it seems to work well. Thanks!

Awesome, thanks Geoffrey and Zach! I'll leave this issue open to track the proper fix, but we'll go ahead and document session_refresher.

I tried both solutions and the second one work for the desktop browser. But my main application is using via android tablet with "<meta name="mobile-web-app-capable" content="yes">". So it open on a separate full screen window. I tried to load the page[my_app/_gcp_iap/session_refresher] on main chrome browser but it is not working.

Any idea how can i achieve this workaround on mobile web page?

any updates on an ETA for a fix without the workaround?
we use this to supply access to applications we do not have direct control over and adding an iframe in them is not an option

#7: I'd expect the iframe solution to work in that environment, though I haven't tested it. I don't suppose you're able to use https://cloud.google.com/iap/docs/authentication-howto#authenticating_from_a_mobile_app ?

#8: Understood.  No ETA at this time, but it's a high priority.  I'll post any updates here.

The workaround is now documented: https://cloud.google.com/iap/docs/sessions-howto

I tried "Modify your application code to handle the HTTP 401 response." step that include in the document. But I keep getting the following error.

"(index):1 Failed to load https://accounts.google.com/o/oauth2/v2/auth?client_id=643514917173-c9ai54k0e8ng6hkgpbqnhogf20k2tt7p.apps.googleusercontent.com&response_type=code&scope=openid+email&redirect_uri=https://[mydomain_here]/_gcp_gatekeeper/authenticate&state=CkBodHRwczovL3NnY29udHJhY3RnY3AuY29yZGxpZmUuY29tL3NlcnZpY2VzL2NoZWNrLWNvbm5lY3Rpb24uc3ZjEjBBR1k1bEFLb0s1RGRxTEdKX2dYQ2V6R2pRZm4tN0REVGFnOjE1MTczNjg1NzU2MDY: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://[mydomain_here]' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."

Any ETA for a fix? We also have internal applications we access via IAP that we are unable to edit or add iframes to.
We are starting to evaluate other solutions now, which is not the route we wanted to go.

Appreciate your help.

Hi Paul, I'm sorry this is taking so long.  There's a fix we're considering which I'd anticipate being able to roll out in April that would:

1. Change the IAP session lifetime from 1 hour to 20 hours.
2. Add a check so that, for every request with a valid session, IAP calls out to the Google identity system to verify the following:

2a. Account is not suspended or disabled
2b. Account does not have the 'force password reset' flag set
2c. Account's password was not changed after the IAP session started
2d. Does *not* check that the user didn't "sign out" of the Google session that was active when they started their IAP session (we may add this in the future but we're considering skipping it for now to get this rolled out sooner). This means that an IAP session would be valid for up to 20 hours after the user signed out of Google. IAP sessions can be separately logged out by going to https://DOMAIN/_gcp_iap/clear_login_cookie. (Note that if a *Google* session is still active, anyone with access to the browser can log back into IAP after /_gcp_iap/clear_login_cookie without re-entering a password or second authentication factor.)

That is to say, the IAP session lifetime would increase to 20 hours and we would additionally verify 2[a-c] on every request. The reason we've left the current session length capped at 1 hour in spite of the pain this causes for AJAX is that today we do *not* verify any of 2[a-d], and we rely on the Google identity system to check these properties when IAP establishes a new session every hour.

I'd love to get some feedback on this. In particular, are there existing IAP customers for whom increasing the session length to 20 hours would be an unpleasant security surprise? Would the answer change if we added a check for (2d)?

Also, if you're willing to take (1) *without* any of the additional checks in (2) -- a 20-hour session lifetime where IAP sessions will be valid for up to 20 hours after an account is suspended or disabled (e.g. employee exit), password is changed (e.g. account compromise), or user signs out of Google session without also signing out of IAP session (e.g. shared browser / shared computer scenarios), it's *possible* that we could implement that sooner (probably in the 2-3 weeks timeframe) and put it behind a project-specific whitelist (e.g. the change would be off by default but we could whitelist specific projects for it.) Let me know if that's something you're interested in.

Re: #13

Thanks for the update. If I understand what you're describing, we'd still have to use the session_refresher tab in our case. One of our primary uses for IAP is for unsecured internal utilities (e.g. Prometheus monitoring dashboards that are on wall-mounted screens). The 20-hr session would mean we'd still have to re-log in every day.

A 30-day session like gmail (GSuite generally, I guess) has would be fine for our case.

Hi Matthew,

2[a-c] all seem like great changes, and would satisfy a lot of concerns around using IAP with more sensitive data. In light of those, 2d seems like behavior that we wouldn't mind, but don't have a particular need for.

We tend to prefer longer session lifetimes, and I think we'd always be happy with 20+ hours as long as check 2a happens on each request. (We'd love pretty much anything up to 30 days.)

One additional check that would be useful with a change to longer sessions is whether the user is still on the project's IAP user whitelist. Invalidating sessions after a user's account has been disabled / suspended seems like the highest priority from a security standpoint, but a more common use case might be removing a user's access to an application by taking them off the whitelist (or removing them from a whitelisted group). For example,  an employee changes departments and still has an account, but should no longer have access to their previous department's apps.

Thanks for the feedback, Michael and Zach.

Zach: Correct that you would need some page-refresh mechanism for that use case. Request for gmail-esque session length noted.

Michael: We're already doing an ACL check on every request, independent of the IAP session length. (The session length we're talking about here only applies to authentication, not authorization.) There's some caching involved so access revoke isn't instantaneous, but off the top of my head I think access revoke should typically take effect on the order of minutes.

Hi, sorry for the delay here, this is taking longer than expected. We're still working on implementing the #13 checks, but there's a temporary workaround that we can turn on for specific projects if anyone wants to try it. The way it works is, we attempt to detect whether a request is an AJAX call or not, and *for AJAX calls only*, we have an increased session length *without* the additional checks described in #13.

From a security standpoint, this has some risk. An attacker who obtains an IAP session cookie could trivially issue a request that appears to be an AJAX call (e.g. by adding "X-Requested-With: XMLHttpRequest") to trigger the increased session length. However, if you have a limited-sensitivity application where you're willing to turn this on until we can get a better solution in place, send me an email with your project number and desired session length (it's configurable per-project, so we can set it for 30 days, Zach): cloud-iap-session-length-increase-request-external-apr2018@google.com

The proposal from #13 is now ready for testing, please contact cloud-iap-session-length-increase-request-external-apr2018@google.com if you'd like to try it.

The iframe solution e.g.  e.g. <iframe src="/_gcp_iap/session_refresher" style="width:0;height:0;border:0; border:none;"></iframe> was working well for us but recently we've started to get issues.

Users are receiving an error message saying:

There was a problem with your request. Error Code 13.

This happens once / twice a day for a user.

If the user hits refresh in the browser and tries the same action again it all works fine.

Any progress on a permanent solution for this issue? It has been quite some time since this was last updated.

I have noticed in our use case that sometimes a simple refresh does not solve the timeout issue. If we navigate to our IAP protected app and create a session, then close the app tab and come back some hours later, the app will load but all AJAX will return 401. We also see similar errors to #11. Subsequent refreshes do not resolve this unless the user performs a "hard refresh" (Ctrl + F5). The iframe session refresher does appear to work for long sessions on an active tab of the app despite this issue.

At long last, this issue is fixed. IAP sessions for all applications will be valid as long as the underlying Google login session is valid. You should no longer need to use the "/_gcp_iap/session_refresher" mechanism.

Thank you for your patience!

I have a Twitter thread with more background and technical detail on the solution if folks are interested: https://twitter.com/mattsachs/status/1136327101731049472

This link https://twitter.com/mattsachs/status/1136327101731049472 is no longer working, do you still have details on this?

We are having similar issues, would like to resolve it.

I habe noticed thats lest say yoy type out a test message but dont send it, then back out to the previous screen, then click on the message thread to bring the conversation back up with with whats yo have already typed. It wil then have the misspelled words underlined. Still really needs to be fixed though because this doesnt work for everything

Honor 7X Nougat Gboard - no red lines under misspelled words.

Yup Same issue on Samsung S9

pixel 2 xl. missing totally obvious errors and auto correcting correct words to words that make no sense in context of sentence

Was on Pixel, no red underline for ANY misspellings. Now I'm on the S9+ latest update, same deal. Switch to Samsung Keyboard or any other one shows a red underline for misspelled words.

No RED line anymore under the misspelled words using Gboard on iPhone

same issue on Huawei P9 Lite

Using an old build from July of 2017 brings back the red underline. I don't have the time to test every version, but I started noticing its disappearance in December. It came back after a phone reset. As of February, it doesn't work at all

spell check completely not working on my pixel 2 using gboard. i attached my phone and gbiard info.

this issue has been consistent since February.

Oneplus 5t Oreo 8.1 Gboard - no red lines under misspelled words.

This is still a major problem, especially for those of us conducting business over the Pixel 2....

Problem for me as well. 8.1 Pixel 2. Just bought the phone and Gboard updated from factory, which I think created the problem of no red underlines. I uninstalled the update and now spell check is working again.

I am having the same issue where mispelled words are not underlined in red.

Pixel 2 XL 8.1.0
Gbord

So this was reported late January, its curious this is still an issue.

google pixel 2 android 8.1.0 google pixel gboard english spell checker not working at all

Recent update to gboard and issue still occurs. Android 7.0 Moto G5 english brittish.
Noticed that if I add an emoj the red lines appear then if emoj is deleted the red lines go away.

Still happening, very annoying on samsung s8! Keep resorting back to my samsung keyboard for now.

The same problem on xiaomi redmi

No spell checker red underline on Huawei P9 lite.

Same issue on LG V20

Gboard not showing red underlines under misspelled words.
Using Huawei Mate 10 lite.
Fix it asap please.

Same problem here. Hopefully the next update fixes it

Thanks. I assume that it will work after the next update. When one can
expect it?

Regards, M.

On Sun, Apr 29, 2018 at 10:08 PM, <buganizer-system@google.com> wrote:

--
Michael Reznikov
Solid State Institute
Technion, Haifa 3200003
Israel

Phone: 972 48292440 office
           972 48294837 lab

GBoard not showing red lines on Verizon Galaxy S9+

Makes it difficult to send work emails.

I loved my Google Pixel, I was sure I would use Google phones from this phone onward. I've had issues with my hands and have been using talk to text, it misspells words now. The red lines are gone. Can't wait to ditch this phone because of this. Going back to Samsung if this isn't fixed in the next week, which judging by the dates of this thread is highly unlikely. Goodbye Pixel :(

I have been using Gboard (Google keyboard) for years and was functioning perfectly. Lately i updated it to the latest and noticed that there's no spell checker functionality which is annoying as I'm using swipe (glide) all the time and mistake is annoying as i have to double check every word twice

Same issue here... Google Pixel 2 XL / Android 8.1 / build OPM2.171019.029 running gboard 7.1.19.194335471-release-arm64-v8a

Same issue on a Samsung Note 5 after latest update.

*FIXED*
On an unlocked Galaxy S9+ on Sprint, I wasn't getting a red line.
I uninstalled GBoard and installed an older version:
https://www.apkmirror.com/apk/google-inc/gboard/gboard-6-9-8-183626756-release/
It works perfectly, even seems better in other ways.
Now I have set updates up manual, and just don't update GBoard.

I just received another Gboard update on 5/2/2018, and STILL NO FIX for the lack of red underline beneath misspelled words. This is ridiculous! How can Google not fix such a simple, long-standing issue?!?

I oped in for Beta. Still not fixed. :(

3 weeks into the Pixel 2 and ready to return it and go back to iPhone...

I'm dyslexic and NEED my phone to tell me when words are misspelled. Why this isn't fixed is beyond me.

Same, this is annoying!

Same here for months now. Started on my Samsung Galaxy S7 edge. Tried really everything to no avail. Meanwhile I renewed my phone. Shocked to see my brand new out-of-the-box clean installed Galaxy S9+ has the same issue. That's when I knew it's the app itself. Finding this thread confirmed it. So not-Google, but also really not-done in 2018, you can't do this Google, so fix ASAP!

Nexus 5 and everything up-to-date. Spell check of any kind has been non-existent for months and it's getting really annoying!

That said, my spelling is slowly getting better on its own, haha.

Almost 4 months and still no word on this issue? I could see if this was something that wasn't working before, but come on google. Status update?

Still no red underline to highlight misspelled words. Clearing data to go back to old version does not work anymore. Just great

Not working for me. Pixel 2 XL Android P beta preview 1.

Spell check not working on LG G6.

On Tue, May 8, 2018, 6:00 PM <buganizer-system@google.com> wrote:

Not working for me redmi 4x uk

Tryed for few days now. Use it alot but no readline under no misspelt words :(. Whats happend please fix. Uk

Redline not working on my pixel

I miss you red line...please come back.
Pixel xl 2

Same here. Galaxy S9+

Screw it. I installed a new KB. I just now how have to get it to learn my
frequent use of swear words. Ducking Shut!

On Sat, May 12, 2018 at 10:37 AM, <buganizer-system@google.com> wrote:

Ditto on LG V20.

my spelling check is gray out

Alo doesn't work on Android P on Pixel 2 XL.

Wow, I've been defending Google, loved pixel xl. Just got pixel 2. What bothers me more than this bug is the silence from Google. This is a major touch point for the whole experience of the os. If not fixed users are going to fall away fast and there is nothing I can say.

That's exactly what I mean by So not-Google, but also really not-done in 2018, you can't do this Google in my comment #59. Even third parties are publishing articles about this now while Google hides in silence. Not a very smart strategy while knowing there are tons of alternatives out there. But even worse is losing the trust of so many Google fans. Because I think this attitude really is a trust- killer.

No redline on Pixel 2

Such a waste of users and thus market share...

Gboard spell checker is broken: here are the best alternatives
https://www.slashgear.com/gboard-spell-checker-is-broken-here-are-the-best-alternatives-01529220/amp/?__twitter_impression=true

Another Gboard update today. Still no red underline. WTF...

Same issue here pixel 2 xl. Back to iPhone I go. I can't work on this pos.

How exactly Google broke feature that was working perfectly? I am very mad at them... Today there were another update of the app, but still no red underline!

I hate to say this really damaged my confidence in Google, especially since I have a troubled problem too in Google Calendar. If anyone here also uses this app, maybe you wanna take a look at my reported issue at https://issuetracker.google.com/issues/79311041 and comment if you too want this feature back? Thanks!

since here, mine also doesn't work

Unlocked S9 not working. Have to change keyboard to another that works.

I'm having both issues too: red line not appearing, and common misspellings not caught

On a Pixel 2

I feel I've tried every option and still cannot get the red underlines to function again. I spent a lot of time searching the web without any luck.
Samsung Galaxy S7
Android 7.0

Likewise for both issues, and glad I'm not the only one!

Nexus 6p, Android 8.1

Why on earth isn't Google communicating here?! It's silence really begins to feel like an insult. During my attempts to get this to work I encountered some really strange shit too, like this one. Take WhatsApp and type a misspelled word followed by space in any contacts text field. Now enter an emoticon, say 💡. What happens?!?!

Misspelled words are not showing with redline eveb after trying every settings

The red underline does not show since I first got the Pixel 2 XL in  January.

Same issue since Android 8.0 Stable, all the way to P Beta

Not a solution, but noticed that the spellings (and red underline for mistyped words) kicks in after you place a symbol e.g. 😁

That's what I mentioned in message #87 but that only works in WhatsApp and not permanently. If your type on it shuts down again.

Message #87 and #91 don't work for me. It seems that only some people have this "workaround".

Don't worry about it, because it isn't really a workaround. If you type on, the red line vanishes again. Sometimes after 3 words, sometimes a few more. It's hardly an option to add an emoticon every 3 words, check for the red line, remove the emoticon and repeat the process. Not at all reliable. THE REAL SOLUTION MUST COME FROM GOOGLE. HELLO GOOGLE, COME IN PLEASE...

Gboard not underlining misspelled words

Gboard doesn't underline misspelled words.

⁣Sent from BlueMail ​

On May 23, 2018, 9:37 AM, at 9:37 AM, buganizer-system@google.com wrote:

Please fix. This has been an annoying issue for a while now.

Please, give listen to the community and give an official answer Google. Please acknowledge the bug and give an ETA for the fix.

Samr isue on a pixel 2 (misspelled words in this post had no underline!!

Google, just do it.

Same issues with Moto G4+ (Android 7.0)

I have a Motorola X Play with Android 6 and Gboard 7.2.9.197069278 installed. I tried to see if the problem is with the latest version but also is affecting the Google Keyboard from factory. When updated again to the latest version, I see that Dictionary in Configuration it doesn't show you the synchronization of learned words with google account. I'm using suggested words while writing like a workaround.

droid max the update has wrecked my phone. now cant use spell check. few apps do not work with this update. will be running away from droid phones.

I have been experiencing it too. Lately quite many updates have come, but this issue is still not addressed.

Gboard will not underline misspelled words. Samsung S9±

Well, I don't have Samsung s9. It's another model. So wouldn't it work on
that too?
On May 29, 2018 8:05 PM, <buganizer-system@google.com> wrote:

Motorola Moto G 4G, Gboard not underlining misspelled words. Uninstalling updates gets it working again but not the best solution.

Lenovo A6?
On May 29, 2018 8:11 PM, <buganizer-system@google.com> wrote:

Can't say for sure, because Google hasn't responded in any way so there's no info on causes and culprits. Maybe the device makes a difference, maybe not. On my out-of-the-box brand new fresh installed Galaxy S9+ I can't possibly get it to work.

Isn't there any way out?
On May 29, 2018 8:14 PM, <buganizer-system@google.com> wrote:

Gboard is not underlining misspelled words on iPhone 7.

"Isn't there any way out? "

Swiftkey! kappa

Afraid not, except maybe for downgrading by removing updates (which isn't possible on my S9+) or considering another keyboard.

Alright! Thanks.
On May 29, 2018 8:20 PM, <buganizer-system@google.com> wrote:

I have red underlines missing for two anguages, latest Google play build, android 7.1

Same issue as others, no native spelllchecking feature when using Gboard. Am on an 8.0.1 build of Android, OnePlus Oxygen-based ROM.

Somebody knows what is the last working update? I’m going to downgrade gboard using a previous version of the app

Same problem here, with a Xiaomi Mi A1, I found this really anoying.
I'm from Perú, so I use it in spanish, but is the same problem. The Mi A1 is pure android (android project) but still the same problem. I've tried to uninstall and install back again the gboard, didn't work..

Same with Note 8

Having the same issue on my S7, no red underline.

#117 "Somebody knows what is the last working update?"

6.9.8.183626756 works fine.

https://www.androidapksfree.com/devapk/google-inc/gboard/

All the later versions don't work for me.

Are they ever going to look into this? Just switched back to Gboard after years of using Fleksy because I thought maybe I don't need a third party keyboard anymore. But this is a basic function and I don't see any indication it's being addressed. Pixel 2.

Same on Pixel 2 XL running Android P. Had same issue on Oreo too.

Same issue using a OnePlus 5T with Oxygen OS 5.1.2 / AOS 8.1.0.

Really annoyed I started testing Gboard on as many devices I could get my hands on. If necessary I installed Gboard. In the end there were 17 devices owned by family members, friends, colleagues, acquaintances etc. on which Gboard spell check DID NOT WORK. The total number of devices I had processed was..... 17! Damn! That's a 100% NEGATIVE score! Now I'm annoyed even more, especially because GOOGLE HAS NOT RESPONDED NOR CONFIRMED NOR DENIED IN ANY WAY YET, AS IF WE DON'T EXIST TO THEM. LET ME REMIND YOU GOOGLE THAT WE'RE THE REASON OF YOUR EXISTENCE, SO SHOW SOME MANNERS AND LET US KNOW WHAT'S GOING ON WITH GBOARD!!!!!

Still an issue here.

Same issue here. Moto x4 Android 8.1.0
No red line under misspelled words, obvious misspellings with no correction options.

What is it going to take to get Google to pay attention to this?!? I've filed bug reports, submitted feedback, rated the app. Some kind of acknowledgement from Google would be nice

"What is it going to take to get Google to pay attention to this?!? I've filed bug reports, submitted feedback, rated the app. Some kind of acknowledgement from Google would be nice"

Get a few million people to sign in to google and click the star in the top left of this page?

That's it! Yes please.

Same problem here. I am on Nokia 6 2018 running android one.

Same prob here, xiaomi redmi note 5

Same issue here — no red lines and an overall decrease in quality. (Lots of errors getting through that used to get corrected.) Using a Sprint LG G6 that was just recently upgraded to 8.0.

I've even seen a few outlets cover this..

Still not working here. Galaxy s8+

I do not have red lines on my Galaxy S9.

I have a Galaxy S7 Edge Android and have experienced the same problem with red underlining. When I need a serious spell check, I switch the keyboard to Grammerly. it's easy to quickly toggle between the different keyboards. Just hold the language bar for a few seconds and a window will pop up with the choices for keyboard, so you can easily switch back and forth. Google please fix this bug.

Same issue with mine. I had no choice but switching keyboards. I use swift
key just to have spell checking. I dislike the layout of swift key. Hope
gboard can be fixed soon.

On Mon, Jun 11, 2018, 11:33 AM <buganizer-system@google.com> wrote:

maybe not fixing this issue  is Google's way to get us all to use speech-to-text more, in order to collect more voice recognition data on us..

I also have this issue. Gboard was my favorite... Checking so store for good alternatives

Nexus 6p, OnePlys 3t and LG V30+ have this issue
This is very annoying

This was reported on January 23rd and Google's latest follow-up was this:

dn...@google.com  <dn...@google.com>  #4 Jan 30, 2018 01:44PM
We have passed this to the development team and will update this issue with more information as it becomes available.

There were no updates since, or any response by Google at all for that matter. In my opinion that's an act of disrespecting it's clients on Google's part. I think it's a disgrace the way Google acts. I just want to know if the bug is being acknowledged and when it will be fixed. That's all!

My suggestion will be to start all over again and return to the beginning. Our contact here would be dn...@google.com and I guess this person is responsible for maintaining user contacts out here. If you agree, please report not only your issue, but also make a complaint regarding Google's attitude and remind Google of it's moral obligations to it's customers and users. Maybe the press will discover a story in here...

I want the red line coming for incorrect spelling. That's not happening with the GBoard. Please do something about it.

Agreed with the previous comment - would be nice if the red underline that
shows a misspelling would be re-enabled.

On Wed, Jun 13, 2018 at 12:51 PM, <buganizer-system@google.com> wrote:

Huawei Mate SE
Android 8.0.0
Cannot enable spell check

June 18, 2018 update still has no red underline. But hey, new languages and stickers. Just what I needed...

Have the same issue. Is this bug planned to be fixed anytime soon?

Google says: "   ".

Been broken since I purchased a Google Pixel 2 device and came over from Apple. What's a good alternative keyboard?

Re comment #149
A good alternative is Swiftkey.
https://play.google.com/store/apps/details?id=com.touchtype.swiftkey

How to enable swiftkey red underline?

Swiftkey is nice, but it always adds spaces after punctuation, and that's utterly annoying. Using default Samsung keyboard now, and hoping google fixes spellcheck someday.

6 months and this is still an issue. . .how has this not been corrected yet? Has there been any word from google that they are working one this or any reason why this issue exists and is taking so long to correct?

Check my posts here and you'll see that I'm pissed because Google hasn't responded at all so there's no information whatsoever on those subjects 😡😠🤬

I contacted Google support a few days ago through the chat function on the Google One app. Basically, the answer that I got was that they're working on a fix for the issue for the Android P release. No word as to when the Android P release will happen, or whether there may still be a solution coming for Android O. So apparently they're aware of the problem and are taking steps to fix it, but there's no guarantee yet how long it will take or whether you'll need to have Android P in order to get the red underline back. Not the answer I was hoping for, but I guess it's an answer. For the record, the Google One representative that I chatted with was very helpful and easy to talk to. Even though I had to wait a long time in the queue, I was happy with the support I received.

Well, it certainly isn't fixed for the current DP Android P release, with the latest beta Gboard version.

Same issue with my Samsung S9+ Thanks for the suggestion of SwiftKey. I used that with Google Spell Checker and it works!. I turned off Auto-correct in SwiftKey and turned on Spell checker through Language and Input through the General Management of the phone settings.

This worked!

Thanks!

On Mon, Jun 25, 2018 at 4:54 PM, <buganizer-system@google.com> wrote:

--

[image: photo]
*Travis Bradley*
Solutions Partner Manager, Amplitude Analytics
415.712.5041
79 Madison Ave, New York, NY
www.amplitude.com

Hi, same here.
Workaround: When switching out and in of the SMS app, with the square button then selecting the SMS app, it makes the red underlines appear (it works better than switching to another app then SMS again).
I'm using chomp sms 7.20 and Gboard 7.3.12.201473387
On Android 7.0.
I also succefully tested this with the default SMS/MMS v7.0.

I contacted support and they do not seem to care that my phone is basically useless for work now as my spelling sucks!  Would love to see an actual fix and not a BS excuse.

"As of now, the red-line doesn't work in the Gboard app. It was available in the previous versions. However, it is not available in the latest version of the app. I would recommend you to file a feedback for the same so that it reaches the development team. "

I believe it'll be appropriate for Google to replace Gboards descriptive text in the Play Store by something like "actual working spell check feature coming to you in a future Android release, maybe even (but not probably) P but most definitely in Android Z!"

I am also having the issue where red underlines do not appear, but would like to add that I believe this is also interfering with the ability to add new words to the user dictionary. Without the spell check functionality the only way to add new words is manually at the system level. This is a huge problem. Can anybody else confirm this behavior? Try typing something like a username (catnip720) and see if you can get your keyboard to remember it, because I can't unless I add it manually in settings.

Hi google team, same problem here. The spell check, Auto Correct, Auto word suggestion all were working before. Why this simple issue is not fixed even after many people complained?? Disappointing

Same for me to. No underline words. Will be forced to use other keyboard. Jdjdjdkd - example.

I been waiting for a fix since I started using oreo. I'm using a oneplus 5T with Oreo 8.1

Yup seems to be a long running issue

On Sat, Jul 7, 2018, 11:48 <buganizer-system@google.com> wrote: