After upgrading to 3.1.3, the dynamic display of PWA suggestions quit showing in the Editor or anyo other pane (such as Synopsis or Notes). While it appears that PWA Everywhere is still luking in the background, and you can call up the suggestions by opening it, it is easy to find what the suggestion means and where it is in the Editor.
This is a major inconvenience and has been experienced by a number of people who just upgraded. I had to roll back to 3.1.2 to get it working properly again.
Yes, Iâm seeing this also.
you might consider this a ProWritingAid problem, not Scrivenerâs, and should contact them
acronyms make even someone very familiar with âPWAâ to not parse right away
thought there was a workaround, but doesnât actually function, so redacted
No, I get the buttons, etc. The problem is different. And it is definitely a Scrivener bug. ProWritingAid works as it always had in Evernote, Plottr, Word, my Chrome browser, etc. It works on 3.1.2 and does not work on 3.1.3. Tested each step of the way and on two different machines for both versions.
Iâm not sure I understand why you see this as a Scrivener bug.
Scrivener has never had special âhooksâ for Pro Writing Aid (or any similar app), so thereâs nothing that we could have âbrokenâ in the latest version, and nothing that we could potentially do to âfixâ the problem.
Edit: Looking at the Scrivener 3.1.3 release notes, the most potentially relevant change was an update to Scrivenerâs underlying development frameworks. Perhaps you should ask the PWA team about their support for Qt 5.15.11? Scrivener Release Notes | Literature & Latte
Iâm getting the same issue. ProWritingAid used to show me my suggestions in my scrivener document, while i was typing. As soon as i updated yesterday to the new version this is no longer happening. Yes, I have the ProWritingAid button that shows us at the bottom and i can click on it, it will show me my suggestions, but when i try to click on a suggestion it canât display it. I get a message that it is on finding it on my page and then all the suggestions go away.
I did contact ProWritingAid, and Iâm waiting to hear back, but this happened as soon as i updated scrivener 3, so i donât know who to contact.
I going to try to roll back to the previous version because the Fixes listed above would not work from me since i canât even see my suggestions
.
Update: I went and rolled back my Scrivener to the previous version and now everything works properly. I feel like Scrivener and ProWritingAid need to chat. lol Something with the update is not working between the two.
Yeah, something changed on the Scrivener side of the API. A quick chat between L&L and PWA should sort it. I have reported it to L&L and you to PWA, so hopefully will be working again soon.
There is no Scrivener âAPI.â There is no supported way to directly edit a Scrivener project other than Scrivener itself. As such, âScrivener compatibilityâ is entirely the responsibility of third-party programs that purport to have it.
Shipleyaust ⊠were to get instructions to roll back to3.1.2? Thank you!
save all your current projects and note current backup folder and location of project files . I would suggest exporting current theme and preference to reuse. Use windows to uninstall 3.13 and then download and install 3.12. No big deal did myself.
go to this address and scroll down and will see previous versions
https://www.literatureandlatte.com/scrivener/release-notes?os=Windows
Yes, I did. See GoalieDad response to find link to install a previous release.
I played with this a little further, and realized the workaround orignally stated doesnât actually follow through with operating fully, nor does a variation.
Indeed, though you can get the suggestions to show, clicking one doesnât offer anything, just blanksthe list again.
The ProWritingAid app itself continues to work fine when you open it on your project, which give you a way to have the abilities without backing up to earlier Scrivener.
It also underlines that @kewms Katherine has it fully right â they are going to have to upgrade their plugin.
Here is the Update from PWA EverywhereâŠ
Thank you for your patience! Below is the update on the situation. 
As you might have noticed, Scrivener recently released a new version (version 3.1.3). As users are updating to this new version, they are finding that PWA Everywhere is not functioning as expected.
Initially, PWA Everywhere appeared within Scrivener with an indicator of the number of suggestions that should be found within the userâs Scrivener document, but no list of what these suggestions were in the sidebar, nor were there any highlights showing these suggestions.
We have now released a fix that should allow for users to see the suggestions listed in the sidebar. Users should be updated automatically. However, if you are not seeing the suggestions listed in the sidebar, please try restarting PWA Everywhere to allow it to update. Unfortunately, we have yet to find a way to restore the highlighting of PWAâs suggestions. This will take some time for us to fix. Please rest assured that we are reaching out to the Scrivener team to see if we can restore full functionality.
In the meantime, if you wish to restore full functionality between PWA Everywhere and Scrivener with highlights included, we recommend you temporarily revert to the previous version of Scrivener (3.1.2).
We apologize for any inconvenience and appreciate your patience while we work on fixing this for you and other users!
Hey there Steve,
Sarah will still be handling this query. However, I wanted to provide our most recent update so you donât have to wait for one over the weekend. Please see the below.
As you might have noticed, Scrivener recently released a new version (version 3.1.3). As users are updating to this new version, they are finding that PWA Everywhere is not functioning as expected.
Initially, PWA Everywhere appeared within Scrivener with an indicator of the number of suggestions that should be found within the userâs Scrivener document, but no list of what these suggestions were in the sidebar, nor were there any highlights showing these suggestions.
We have now released a fix that should allow for users to see the suggestions listed in the sidebar. Users should be updated automatically. However, if you are not seeing the suggestions listed in the sidebar, please try restarting PWA Everywhere to allow it to update. Unfortunately, we have yet to find a way to restore the highlighting of PWAâs suggestions. This will take some time for us to fix. Please rest assured that we are reaching out to the Scrivener team to see if we can restore full functionality.
In the meantime, if you wish to restore full functionality between PWA Everywhere and Scrivener with highlights included, we recommend you temporarily revert to the previous version of Scrivener (3.1.2).
We apologize for any inconvenience and appreciate your patience while we work on fixing this for you and other users!
(Basically, reverting to the previous version, as you did, is the best work-around for now.)
Sincerely,
Kyle
Haha, posted within a minute of each other.
I think theyâve completed the full fix â just tried it, late this night, to see if there was a way to use the intermediate they noted about, and as I am seeing it, suggestions are now highlighting again, in the Scrivener pane.
next day note: Iâm not sure, but the highlighting method may have changed. I seem to remember it being underlining - now itâs a block-brighten on the word/s style, which works at least as well, in fact nicer at least as felt hereâŠ
The same thing happened with Grammarly after the recent update.
Hi Keith. Iâm in the PWA âPower Userâ group and was talking to PWA about this. I agree with you that itâs likely a regression test failure on PWAâs part. But users are being bounced between the two vendors support teams. Not a good look on either side. Would a regular dev team hook up between PWA and L&L solve these kinds of issue more promptly? Youâre partners right, not competitors?
Sounds like PWA know the cause of the problem. If so does it require a change to Scrivener to resolve and they reached out to L&L and rebuffed? Sounds like that is what is suggested. Hope not.
Is this issue really [solved]?? Trying to bang vendor heads together on this topic via PWAâs Power User group. Frustrating for us users to be stuck in the middle here, trying to figure things out⊠: Log in