-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client unable to fetch update on local machine hosted inside local network (linux server) #21
Comments
@lfrallon seems like your problem is caused by azurite, When you test to download the code-push update from server, the server returning blob url with azurite host as is. And that's why your mobile device can't connect to 127.0.0.1 of your host machine. it just simple code-push-server fork, i'm just adding ENVIRONMENT var "AZURITE_CONNECTION_STRING" to customize azurite connection string you just need to customize the host of azurite connection string (maybe use your local wifi address for your machine), and tune up your azurite setting if needed. |
@azrulhaifan that's also what I thought. Thank you. I'll check it then and also currently looking for different solutions. |
Hello, there! I am using your fork, but when I am trying to login, I am gettting the following error instead of the access key
in my browser, here is my .env file with AZURITE_CONNECTION_STRING EMULATED=true and how do we use the blob storage solution that you pointed out? |
@alisyd I think you need to register again like |
try to re-register like what @lfrallon say, or logout than relogin. if you can't achieve it, try to remove your CLI profile manually.
if you setup a correct AZURITE_CONNECTION_STRING, than your codepush server will serve the blob url (for downloading code update) from it, you just need to make sure the azurite server are published & can be accessed via internet. and take a look your connection string at : i think the correct string is : one simple way to make sure your azurite blob server are exposed to internet is by access your IP:PORT on browser, than it will show xml page |
Yep that was it, Changed the connection string and things are working fine. Thanks for the help! |
Hello @alisyd @azrulhaifan @lfrallon What should I give to
If the AccountKey is incorrect, the codepush server will throw the following error:
Thanks in advance. |
AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==; I changed the IP and port for queue and table and blob and accountKey, However, It still see 127.0.0.1 like below when downloading. ㅜㅜ
@alisyd @azrulhaifan @lfrallon What could have gone wrong? |
Using Azurite connection string in .env works with @azrulhaifan fork of code-push-server, if you are using the one from this repo, It would not work |
Hello, I cloned this repository below. https://github.com/azrulhaifan/code-push-server-freedom.git .env
I gave it 0.0.0.0 to accept remote requests.
Checking for updates was successful, but downloading still fails with IP address 127.0.0.1.
|
@puresprout Did you resolve the issue with downloadUrl being directed to local (127.0.0.1) |
@simonadenic |
@azrulhaifan thanks for the forked repo. Can we host the azurite server on a different machine? I am trying with your changes on azure-storage, and hosted azure on a different machine. I am able to get the xml response on curl request to this server as well.
|
Hi there,
I encountered an error when executing
code-push-standalone release-react <app-name> android -d Staging --mandatory true --targetBinaryVersion "<app-version>"
.This is the response of the code push server api:
Though I can see the releases on the deployment history,
react-native-code-push
is unable to fetch the update.Code Push client logs:
Environment Setup
Using local development setup on linux machine (Ubuntu 24.04.1 LTS).
.env
Azurite running on Docker container
docker run --restart always -d -it \ --name codepush_azurite -v $HOME/data:/data \ -p 10000:10000 -p 10001:10001 -p 10002:10002 \ mcr.microsoft.com/azure-storage/azurite
Engine version
The text was updated successfully, but these errors were encountered: