Error Signture issued at time is in the future

[paladinic]

Hi,

I'm working on a rather shinyApp which involves a firebase login.
Until most recently, the app was working but, potentially since upgrading to Windows 11, I am getting this error in the console:

Signture issued at time is in the future

The elements that load with reqSignin do load, but the ones that use f$req_sign_in() do not.

What could this error be referring to?
What could be causing it?

For context, I am testing the same app on the windows machine where its throwing this error and on a Mac where no error is thrown and the app works as expected.

I was able to reproduce this in a smaller shinyapp:

library(shiny)
library(firebase)

Sys.setenv(FIREBASE_API_KEY = "xxx")
Sys.setenv(FIREBASE_PROJECT_ID = "xxx")
Sys.setenv(FIREBASE_AUTH_DOMAIN = "xxx")
Sys.setenv(FIREBASE_APP_ID = "xxx")
Sys.setenv(FIREBASE_STORAGE_BUCKET = "xxx")

ui <- fluidPage(
  useFirebase(), # import dependencies
  firebaseUIContainer(),
  reqSignin(
    h1('Hello')
  ),
  uiOutput("test")
  
)

server <- function(input, output){
  f <- FirebaseUI$
    new()$ # instantiate
    set_providers( # define providers
      email = TRUE, 
      google = TRUE
    )$
    launch() # launch
  
  output$test = renderUI({
    
    f$req_sign_in()
    
    h1("World")
    
  })
  
}

shinyApp(ui, server)

> sessionInfo()

R version 4.3.1 (2023-06-16 ucrt)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 11 x64 (build 22621)

Matrix products: default


locale:
[1] LC_COLLATE=English_United Kingdom.utf8 
[2] LC_CTYPE=English_United Kingdom.utf8   
[3] LC_MONETARY=English_United Kingdom.utf8
[4] LC_NUMERIC=C                           
[5] LC_TIME=English_United Kingdom.utf8    

time zone: Europe/Berlin
tzcode source: internal

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

loaded via a namespace (and not attached):
 [1] jsonlite_1.8.5     miniUI_0.1.1.1     dplyr_1.1.2       
 [4] compiler_4.3.1     promises_1.2.0.1   tidyselect_1.2.0  
 [7] Rcpp_1.0.10        stringr_1.5.0      jquerylib_0.1.4   
[10] later_1.3.1        fastmap_1.1.1      mime_0.12         
[13] plyr_1.8.8         R6_2.5.1           shinyjs_2.1.0     
[16] generics_0.1.3     colourpicker_1.2.0 htmlwidgets_1.6.2 
[19] tibble_3.2.1       shiny_1.7.4.1      bslib_0.5.0       
[22] pillar_1.9.0       rlang_1.1.1        DT_0.28           
[25] utf8_1.2.3         stringi_1.7.12     cachem_1.0.8      
[28] httpuv_1.6.11      fs_1.6.2           sass_0.4.6        
[31] cli_3.6.1          magrittr_2.0.3     shinyWidgets_0.7.6
[34] digest_0.6.32      rstudioapi_0.15.0  xtable_1.8-4      
[37] lifecycle_1.0.3    vctrs_0.6.3        gargle_1.5.1      
[40] glue_1.6.2         googledrive_2.1.1  fansi_1.0.4       
[43] reshape2_1.4.4     purrr_1.0.1        tools_4.3.1       
[46] pkgconfig_2.0.3    ellipsis_0.3.2     htmltools_0.5.5 

Thank you!!

P.S. there is a typo in the word signature.

[JohnCoene]

This is strange, I cannot reproduce it.
@munoztd0 any idea? :(

[paladinic]

I've been meaning to reset my machine for a while, so I might try that and see if it fixes this.

[JohnCoene]

I surely hope a bug in one of my packages doesn't lead someone to formatting their disk... That'd be peak failure.

Surely there is an easier solution we can find :)

Can you first try clear cache/visit your app in incognito?

[paladinic]

Thanks, John,

I tried these suggestions now, as well as different browsers.
Unfortunately, the error persists.

[munoztd0]

@paladinic So to begin, you are not crazy..

Everything fine on linux but got the same error by booting into windows..

This is very weird

[munoztd0]

#65 will be a momentary quick solution that bypass this I will be working on a longtime solution next week

[munoztd0]

@paladinic after looking more into it, I found out that the time on the windows virtual machine were I tested it was not synchronized. So first thing I would check is that your timezone and automatic time is set properly.

On an another note I added the possibility to bypass the error with a yes/no prompt for local development in #70.

[paladinic]

This seems to have fixed it!
My PC was in fact not set on automatic time.
Thank you very very much.