Base solution for your next web application
Open Closed

Unpredictable landing page after admin login #10810


User avatar
0
timmackey created

ANZ ver 8.5.0 (upgrading from 8.4.0) angular/.net Core

Login as host admin. Sometimes the correct nagivation menu and page appears.

Other times the wrong nav menu and page appears.

The correct page or wrong page may (or may not) appear after a 'npm start' or incremental build after minor unrelated source code update. This same behavior is occurring for ver 8.4.0. Deleting localhost cookies has no effect on the outcome. What could be causing this?


5 Answer(s)
  • User Avatar
    0
    timmackey created

    UPDATE: Discovered a pending Windows 10 update. Updated Windows and restarted. Normal behavior.

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @timmackey

    Let's keep this issue open and see if you are going to face same problem again or not in a week or so.

  • User Avatar
    0
    timmackey created

    The problem has reappeared after a minor change in a configuration file (related to debugging). Closed CMD window. Restarted CMD window. 'npm start'. Delete all browser cookies related to 'localhost'. Navigate to 'http://localhost:4200/' in Chrome browser. Same (as above) wrong landing page for no appearent reason. Also tried from VS Code debugger. Same response. How can I debug this? What should I look for? Where can I set some breakpoints and examine variables? What variables? Here is the console log:

    NODE_ENV: development
    [WDS] Live Reloading enabled.
    Angular is running in the development mode. Call enableProdMode() to enable the production mode.
    Client: localhost
    Server: localhost
    NODE_ENV: development
    [WDS] Live Reloading enabled.
    Angular is running in the development mode. Call enableProdMode() to enable the production mode.
    DEBUG:
    Starting connection using WebSockets transport
    DEBUG:
    Starting connection using WebSockets transport
    [2022-01-14T09:56:49.188Z] Information: WebSocket connected to wss://localhost:44301/signalr?enc_auth_token=wNYmO41%2F48SHNstaLVXxHCCre29BZQl1NhC6NM3R3rzpXtPQxVzH6jEzA%2FQhXFN5tu6Fk7pO53uppm1mVXMZgxbyRVz26dnepi%2FFyB6axBY%2B6gq1GL%2BuRQgoiFUCjRN2p8w6LevViwKlHyWZZJZO1DGVSjAi1m2U%2Bog9pkHw9%2FQR4Nl%2FDPnoP9JYDMpZ1zxx09u6s0GZ9%2FQ5Sjk%2BL0UfcSCbl38X8he5w9UIn%2FHvxh7ysM1CiPLsoOwtbiieSRVmrmt0JjnipAn4%2FK283F8GrGwzwgehWsqefmUnM0ckMwP9ZAdwQxWDhxv0IqNw4tDhwUYs%2F1SYdYozdNzgByhgNOBPzQDObNLlWc4vV5VMOibHYbT7kHjizEtaLJKzgv0eAD%2BS0%2Biu5o6Byoikc4PAh1l54PmaInvpmjNyM%2BgeFcb2nhO%2BOdhj9Az%2BBXyYEL%2BATMMVpD1JMMwjKSi6Xn4AKwpoMvuwcPwtyT%2B5V2%2B%2BkFDs3rUZ0hyEjB68lMImPhG3UhwnCKstM1U6HVOTMXMj%2BiEvSwnLIwtbZlStvW55tghqArSKQ0yCl2hBpwDOPtWh7eGc0PXyvx9EJYuDHFn6r7kWxBpXEBlY1f5l4BGJqcKbIMgXin0b0xrZBx5UkpTk69RKK%2BKXbsBYe2L9Dz8npIH%2B6jOy%2Fosclik7gGYiJ9mCj4bQ3D2hxLyjYDMiFuzy3pUnseRrlQNZwhQKuJ5ttFDc6kUg2C2hFIjQDbxA9ktp3bxoHByjAjGDZ%2BOmQT0KYW34s%2BKrTvbbQkG0LATcfm1sbjJSN1YdffEczzIS%2BuOnkanpVKEsT4mQFPyNL7MKO7yfuM3A%2FX71%2Bil2f79%2By6JCUh0ddONqXtzMM%2FgfUCBXYS6WvPv25srtNMtzABcrmM5c238rfGoIVyAXJ3gwuYPU69pQSRkqTv9frOjVj36Sa6Vg4NdQKWwZgLxaT335N8FeZHkEqM9X94snBMaF5ywghhYUTr%2BhnFM2F%2BB0F5GLu1T9phUzcWSKT%2BbFYqe%2FDztpMeL2WU0lxOutWY7FMQ%3D%3D&id=lATfpFevw1w-j4f9cJFOHQ.
    DEBUG:
    Connected to SignalR server!
    [2022-01-14T09:56:50.338Z] Information: WebSocket connected to wss://localhost:44301/signalr-chat?enc_auth_token=wNYmO41%2F48SHNstaLVXxHCCre29BZQl1NhC6NM3R3rzpXtPQxVzH6jEzA%2FQhXFN5tu6Fk7pO53uppm1mVXMZgxbyRVz26dnepi%2FFyB6axBY%2B6gq1GL%2BuRQgoiFUCjRN2p8w6LevViwKlHyWZZJZO1DGVSjAi1m2U%2Bog9pkHw9%2FQR4Nl%2FDPnoP9JYDMpZ1zxx09u6s0GZ9%2FQ5Sjk%2BL0UfcSCbl38X8he5w9UIn%2FHvxh7ysM1CiPLsoOwtbiieSRVmrmt0JjnipAn4%2FK283F8GrGwzwgehWsqefmUnM0ckMwP9ZAdwQxWDhxv0IqNw4tDhwUYs%2F1SYdYozdNzgByhgNOBPzQDObNLlWc4vV5VMOibHYbT7kHjizEtaLJKzgv0eAD%2BS0%2Biu5o6Byoikc4PAh1l54PmaInvpmjNyM%2BgeFcb2nhO%2BOdhj9Az%2BBXyYEL%2BATMMVpD1JMMwjKSi6Xn4AKwpoMvuwcPwtyT%2B5V2%2B%2BkFDs3rUZ0hyEjB68lMImPhG3UhwnCKstM1U6HVOTMXMj%2BiEvSwnLIwtbZlStvW55tghqArSKQ0yCl2hBpwDOPtWh7eGc0PXyvx9EJYuDHFn6r7kWxBpXEBlY1f5l4BGJqcKbIMgXin0b0xrZBx5UkpTk69RKK%2BKXbsBYe2L9Dz8npIH%2B6jOy%2Fosclik7gGYiJ9mCj4bQ3D2hxLyjYDMiFuzy3pUnseRrlQNZwhQKuJ5ttFDc6kUg2C2hFIjQDbxA9ktp3bxoHByjAjGDZ%2BOmQT0KYW34s%2BKrTvbbQkG0LATcfm1sbjJSN1YdffEczzIS%2BuOnkanpVKEsT4mQFPyNL7MKO7yfuM3A%2FX71%2Bil2f79%2By6JCUh0ddONqXtzMM%2FgfUCBXYS6WvPv25srtNMtzABcrmM5c238rfGoIVyAXJ3gwuYPU69pQSRkqTv9frOjVj36Sa6Vg4NdQKWwZgLxaT335N8FeZHkEqM9X94snBMaF5ywghhYUTr%2BhnFM2F%2BB0F5GLu1T9phUzcWSKT%2BbFYqe%2FDztpMeL2WU0lxOutWY7FMQ%3D%3D&id=NvzOOeeXzx-4nuIIbJvdoQ.
    DEBUG:
    Registered to the SignalR server!
    
  • User Avatar
    0
    timmackey created

    Here's another clue: WAIT 9 HOURS. The app is behaving normally this morning. ANZ: could you please suggest some debugging techniquest. Breakpoints? Critical variables to monitor? Thanks.

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @timmackey

    Since we haven't faced such a problem before, it is hard to predict the cause of the problem. Could you move mouse over the menu bar when you see this problem and see if it brings back the menu items ? If that happens, the problem might be related to change detection.