My react-native app has the following problem:
There some rare mobile users who have a same problem on production, but I cannot reproduce it on dev env.
So my approach is releasing code-push with debuggable feature for those users only. Assume that I have those deviceIds or any needed target info.
Can I release code-push for those users only?
or just one device is ok!
Related
I have recently created an app with react-native and my concern is about react-native security. I heard that react-native is not compiled and the code exists as it is in development.
So if we have some sensitive data in variables, what can we do for protecting that?
If you want to protect your react-native app in release, consider the following.
always save your sensitive data in shared preferences on
android and keychain on ios, here is a nice package: https://github.com/oblador/react-native-keychain
use react-native proguard
Encrypt your data and decrypt when you need it.
If possible save your data on server side
Can I manually test an "ipa" or "apk" file generated by Codename One on a device farm, like using a real device?
I have this doubt because, on the AWS Device Farm FAQs, it's written so: «My app is obfuscated. Can I still test my app on AWS Device Farm? Yes, if you use ProGuard. If you use DexGuard with anti-piracy measures, we are unable to re-sign the app and run tests against it.»
I know that the apps generated by Codename One are obfuscated, that's why I don't know if I can use them on Amazon device farm.
We use the default proguard not dexguard so there shouldn't be a problem with Amazon. You can also disable the proguard obfuscation stage entirely with the build hints.
I've been building a website with React and Node recently. I'm currently working on the mobile site. I've been running everything locally and currently test the mobile version with either an emulator (Ripple Beta) on the chrome store or by deploying it via Surge. However, running it on my phone via surge is ultimately different from running it on desktop.
Now before you suggest what may be causing differences I wanted to note also that I am currently implementing the following (based on what I saw in other similar threads):
<meta name="viewport" content="width=device-width, initial-scale=1">
react-responsive package
I want to keep my website single url instead of using an m(dot).link and I also want to use an adaptive design rather than responsive (I'm aware responsive is usually better).
One example of where an emulator will not suffice for testing is for testing compatibility with very specific syntax. For example, iphone does not understand certain es6 syntax such as "new Date()" for certain date formats whereas android does.
Is there a way to test an adaptive design for mobile on desktop such that I can run it locally on my computer instead of having to deploy on surge each time (so that I can open it on my phone).
This will make debugging these kind of problems much easier! I've seen a lot of similar threads for responsive designs but I think adaptive designs (completely different design from my actual desktop website design) can have sort of unique issues as seen above. It would be great, however, if I could still utilize the core functionality/components of the desktop version.
I worked on a school project that required us to test our web app using a real phone. What we did was we host a firebase server.
Start by installing the firebase cli:
npm install -g firebase-tools
Type firebase init in your console. (https://firebase.google.com/docs/hosting/deploying for reference)
Push your code onto your hosting with firebase deploy, then you can go to your url on your phone and it should work pretty well. Firebase deploy would be like a git push, it takes seconds to complete, so it's pretty quick.
Edit: Sorry didn't realize Surge did the same thing. However, I do not think you can test on your computer easily. Though you can download Xcode if you have a Mac and use the iPhone emulator, and Android Studio for the Android emulator. But both take pretty long to start up, personality, I would just deploy to surge or firebase and test on a real phone if you have one.
If your phone and laptop are on the same wifi, you can access your locally hosted web app on your phone.
STEPS
Run your react web app as usual, it'll be available on http://localhost:3000
Go to the terminal and type ifconfig | grep inet. This checks your laptop`s local network IP e.g. 192.168.0.10
On your phone, open your browser and the url http://192.168.0.10:300
NOTE: We replaced the localhost with the IP 192.168.0.10
I have Apple ID. When I am trying to Send IOS app store build in MAC system, I am getting Build Error.
I have created certificates for this, might be this step leads to error{ created certificate with device UDID}.
Please help me on how to create certificates and send IOS store build.
Thanks in advance.
you can directly this all features directly by using netbean. There is wizard "Generate" for ios from which you can create development certificate as well as provision profile. You can also add devices by using the wizard in ios tab.
I have two Google App Enginge application id:s, let's say App1 and App2. App1 is version for beta testers, App2 is public version of the same application. Idea is to deploy application first with application id 'App1', beta test it, and then deploy the same application with application id 'App2'.
I have problems with this sequence:
I do changes for beta testing and deploy it to App1 -> All changed
files deployed OK
Beta testing is done using App1 -> Beta testers are happy
I deploy the same application (just change application id in
Eclipse's 'Deploy to App Engine' dialog) to App2, because I want it
public. Now the problem is that no files are deployed. Is the reason
that there are already the same files deployed to app engine? But
they are in App1, so App2 does not work.
Any suggestions how to do force upload for all files? Or any other way around this problem?
BR, Seppo
Try also altering the version to something not previously used when deploying to the second Application ID. Alternatively it may help to delete the version you're about to deploy to (although you cannot delete the default version). Such changes might flush some cache in Eclipse of assumptions about what was previously deployed.
The uploader seems to transfer only what is newer than the destination. That suggests another potential cause of your problem. Your symptoms might occur if the local computer's clock is somewhat behind the one in AppEngine. It is not very likely, but possible.