63585bd3-9ed8-4472-80d0-1bae5ad3c571

hello!

build and or deploy logs please -
(this is a new version of the log downloader)

1231389678838747236

The main man! hi!

please use the new version of the bookmarklet

gotcha. one sec

1231390179366015006

thats strange, ive sen that error just recently, maybe try another deployment?

okay! trying it now

failed again

build logs again please

1231396076095930439

looks like either github or google is having network troubles

send me your nixpacks.toml file please

1231396616578138132

ah this would make sense. cause i have google0auth.

nope nothing to do with it, unless you mean to say your google auth is now failing lately?

nope it works locally!

try this nixpacks.toml file instead -

# https://nixpacks.com/docs/configuration/file

providers = ['node']

# set up some variables to minimize annoyance
[variables]
    NPM_CONFIG_UPDATE_NOTIFIER = 'false' # the update notification is relatively useless in a production environment
    NPM_CONFIG_FUND = 'false' # the fund notification is also pretty useless in a production environment

# install caddy
[phases.caddy]
    nixpkgsArchive = '727db88c063586d2f912af26dc3ce19d6f31af05' # caddy v2.7.6 - https://github.com/NixOS/nixpkgs/commit/727db88c063586d2f912af26dc3ce19d6f31af05
    dependsOn = ['setup'] # make sure this phase runs after the default 'setup' phase
    nixPkgs = ['caddy'] # install caddy

# format the Caddyfile with fmt
[phases.fmt]
    dependsOn = ['caddy'] # make sure this phase runs after the 'caddy' phase so that we know we have caddy downloaded
    cmds = ['caddy fmt --overwrite Caddyfile'] # format the Caddyfile to fix any formatting inconsistencies

# copy caddy and build artifacts to a new image and start the caddy web server
[start]
    cmd = 'caddy run --config Caddyfile --adapter caddyfile 2>&1' # start caddy using the Caddyfile config and caddyfile adapter

okay updating now

okay it looked like it was about to start working but thenit crashed so i am restarting the deployment

logs please

1231401408507412611

ah

possibly fixed, try again

i did. it crashed again

logs please

it's the same as the one i sent above

1231402903781245049

have you updated your nixpacks.toml file with the one above?

yup

okay I'll try some things

this does work, please make sure you are using it

hey brody! i stepped away and came back and it wasn't crashed anymore

it is up now

when i click "Continue with Google" button that triggers my googleoauth, never happens though. As i mentioned earlier locally this works as expected. do you think this is related to deployment not working?

nope that would be a code issue, check the browser console logs

hi brody!! i got another error:(

1232110459029688421

still learning how to debug from the logs but i think it's because i am trying to use some font awesome icons? I read the documentation about what is needed to use them from web: https://www.npmjs.com/package/react-native-vector-icons#web-setup

This is what I did for step 1:

This is what I did for step 2:

are you able to build this locally?

Hi Brody!

I was able to figure out the font awesome icon issue. It is showing locally and deployed

awsome!

The other issue I am having on deployment is my hooks aren't working

hooks?

react hooks/api calls

do they work locally?

Yup yup

what errors do you get when deployed to railway?

Really strange actually let me get some pics for ya one sec

so i used an api call to get the auth url. the url is triggered when the user clicks "Continue with Google". My console logs are showing the data on the side

Locally:

in deployment my console log returns the html document? haha no idea why

can you send a link to this page so i can see the error for myself

https://www.mykidsleague.com/

well i cant even click the google button lol

clicking does nothing, no console logs and no network activity

really!? interesting. let me redeploy..i think i may have found the issue (fingers crossed)

yeah nvm didn't work haha

so u cant see the console logs ?

yeah theres console logs, just nothing is logged when i click on the button

these are the logs when i load the page and dont click anything

yes the last one is the reason why the button isn't doing anything

it's not retrieving my url from the backend, so there's "nothing" to click on

i think i know whats going on

i assume you are using an service variable to set the backend url?

yes!

are you sure its prefixed with https:// ?

no it's this

i have it currently displaying on the app too

its supposed to be a url value, therefor it needs to be prefixed with https://
i think we have went over this a few times before too 🙂

aw mann

youre so right

i even had that in my notes!

i put it in bold now…ha

i made the adjustment and redeployed. this is just a code issue now right? that i can go look for?

now you are getting a cors error

you may have something in your notes about that? we have talked a bit about that before too

yes i remember cors! i ahve it in my server, but i will keep debugging and see if i can get to the bottom of it

are you sure you have that variable set correctly?

i think so! i used the railway domain cause i thought either or could work. do i need to use the new domain i got?

but thats not your frontend's domain

ideally you use [https://${{.RAILWAY_PUBLIC_DOMAIN](https://${{.RAILWAY_PUBLIC_DOMAIN)}} so that you dont have to worry about manually updating the variable if you change the service domain

thats in your notes too 😉

i know youre right

i think because i recently got a domain/changed it i didn't think to update that…

thanks brody!!

all is working now

no problem!

unrelated - are you familar with assetlinks.json files?

never heard of it

cool. was just curious! thank youu

no problem!

Hi again!

I may have celebrated too early… I tried actually clicking "Continue with Google" in deployment and it gives me an error adter it pulls up the google consent screen

locally it says this and after i continue it goes to my home screen:

in deployment it says this:

then goes to this after:

that means your backend did not respond to that request, check your deploy logs

1232478823992266803

and your backend fully crashes from this error

ah okay

how did u find that so fast haha

all i saw was this giberrish

i scrolled to the bottom

the latest log lines are at the bottom

gotcha good to know

thanks brody that fixed it!

any way to solve naming convention here? or i have to accept it as is?

awsome, but i have no clue why it says railway.app, youd need to check the docs for your 0Auth lib that you use

haha we were on the same page.

i actually didnt use a library. found a cool video where he shows u what everyhing is doing so i created the functions on my own following along

ah interesting approach, then youd need to check google's docs on how to set those names

sounds good

will do that

thanks again!!

yeah the libraries seem to deappreciate and break people's apps from what i was reading

i think there are a few highly maintained 0auth libs

yes for sure

but i was trying to find one for react native web and react native and that i understood and wasnt just copying and pasting

so that limited me haha

ah gotcha

and if you were curious about this. looks like google does it this way until i verify the app through them to avoid pishing

ah that makes sense