Vincil Bishop
05/30/2022, 2:19 PMskan-gd | ts="2022-05-30 14:17:40.388" level=WARN msg="No auth context found" logger=com.gooddata.tiger.grpc.client.AuthContextClientInterceptor thread=grpc-default-executor-120 action=rpc_inject_auth_context method=tiger.ResultCacheService/get orgId=default spanId=bab98ad4f15c0d18 traceId=bab98ad4f15c0d18 userId=demo
There is no error thrown in the browser console.
The ReactDOM reports that the components rendered a second time...if I had to guess I might say that somehow the auth context is missing?
I think I have followed the instructions, and of course at some point on the first render the system obtained a satisfactory auth context because the components were rendered spectacularly. It's only when navigating to a different route containing the same components that they will not render a second time.
For example, this route will render correctly the first time:
http://localhost:4200/organization/1/overview
But when navigating to this route:
http://localhost:4200/organization/2/overview
The components will not render. It is interesting to note, that when navigating back to the first route, the components will not render a second time.
This would be blocking us, so any insight on how to work around this would be appreciated.
Thanks in advance.Vincil Bishop
05/30/2022, 5:13 PMVincil Bishop
05/30/2022, 5:14 PMVincil Bishop
05/30/2022, 5:18 PMVincil Bishop
05/30/2022, 5:24 PMVincil Bishop
05/30/2022, 5:25 PMVincil Bishop
05/30/2022, 5:26 PM<InsightView/>
API that I could call to force the refresh?Vincil Bishop
05/30/2022, 5:26 PMVincil Bishop
05/30/2022, 5:29 PMVincil Bishop
05/30/2022, 5:30 PMJiri Zajic
05/30/2022, 6:56 PMVincil Bishop
05/30/2022, 6:57 PMJiri Zajic
05/30/2022, 6:57 PMVincil Bishop
05/30/2022, 6:57 PMJiri Zajic
05/30/2022, 6:58 PMVincil Bishop
05/30/2022, 6:58 PMVincil Bishop
05/30/2022, 6:58 PM