This is an Ivy bug report.

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

Event with the correct imports and declarations I get the following error

The pipe 'async' could not be found ("
    </div>

    <div class="progress-bar" [ERROR ->]*ngIf="isProgressBarVisible$ | async"></div>
</div>

"):

Expected behavior

It should compile

What is the motivation / use case for changing the behavior?

Just checking the compiler status

Environment

Angular version: 7.0.0-rc.1
 
For Tooling issues:
- Node version: NodeJS 10.12
- TypeScript version: 3.1.3

Others:
This is an *Ivy* bug report. I reported it, because the status page says pipes should work. Feel free to close this issue, if it's not the right time to submit bug tickets. 

I have same problem, and turned off ivy too. The problem is with pipes ERROR in : Template parse errors: The pipe 'date' could not be found....

For turn off ivy, open tsconfig.json and edit the key ivy to false.

"angularCompilerOptions": {
    "enableIvy": false
}

It's failing for other reasons (first could not resolve foreign function declaration: app.module.ts forRoot, after fix Module not found: [object Object]).

Debug on Windows fails: HostResourceLoader: host(C:\Repositories\admin/C:/Repositories/admin/src/ts/components/dashboard/dashboard.component.html) returned a Promise

So I'll leave this here, maybe it helps the Angular developers.

I didn't fix it, turned off ivy. It is still developed actively, eg. #27737

i'm having the same issues using latest angular 8 and angularfirebase

The error Error: Uncaught (in promise): Error: The pipe 'async' could not be found! is still an issue for me as of 9.0.0-next.7

Happens after I save a module (even without making changes to the module). Restarting ng serve fixes it.