* using log directory ‘/srv/hornik/tmp/CRAN/shinyStorePlus.Rcheck’
* using R Under development (unstable) (2024-08-16 r87026)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 18.1.8 (9)
    Debian flang-new version 18.1.8 (9)
* running under: Debian GNU/Linux trixie/sid
* using session charset: UTF-8
* checking for file ‘shinyStorePlus/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘shinyStorePlus’ version ‘1.2’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [4s/6s] NOTE
Maintainer: ‘Obinna Obianom <idonshayo@gmail.com>’

Found the following (possibly) invalid URLs:
  URL: http://66pharm.com:3838/portfolio/shinyStorePlus
    From: README.md
    Status: Error
    Message: Could not resolve host: 66pharm.com
  URL: https://r2apps.shinyapps.io/browserLinkToInput?data=pressure&name=obinna&num=50&outt=wowowow
    From: README.md
    Status: 202
    Message: Accepted
  URL: https://r2apps.shinyapps.io/shinystoreplus
    From: README.md
    Status: 202
    Message: Accepted

The BugReports field in DESCRIPTION has
  https://github.com/oobianom/shinyStorePlus
which should likely be
  https://github.com/oobianom/shinyStorePlus/issues
instead.
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for executable files ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘shinyStorePlus’ can be installed ... [2s/2s] OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking code files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [0s/0s] OK
* checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the package can be unloaded cleanly ... [0s/0s] OK
* checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
* checking loading without being on the library search path ... [0s/0s] OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [3s/3s] OK
* checking Rd files ... [0s/0s] OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... ERROR
Warning: parse error in file 'lines':
17: unexpected '{'
294: # example 3 with dynamically generated inputs
295: if(interactive(){
                     ^
** will not attempt to run examples
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... SKIPPED
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes ... OK
* checking re-building of vignette outputs ... [3s/3s] OK
* checking PDF version of manual ... [3s/2s] OK
* checking HTML version of manual ... [0s/0s] OK
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... OK
* DONE
Status: 1 ERROR, 1 NOTE