Im doing an app for Android. I'm using Genymotion for debug. Everythings working perfectly there.
However, when i'm trying on my phone, the first run after install will go fine. After that i kill the app from the task manager and start the app again. Many of the JavaScripts are failing, some of working, but the weirdest thing is that even alert() not working anywhere.
Anybody had the same problem before? Or any advices? Maybe it's a cache, phone, ROM related thing?
UPDATE
What i've tried so far:
<preference name="KeepRunning" value="false"/>
android:clearTaskOnLaunch="true"
Enable the console plugin of phonegap and watch logcat logs for anything wrong that might have happened.
Couldn't find any real fix in hours. Tried the unaligned version of the APK and it's working fine, so it must be something with the ziptool, i'll try with other ones.
Related
I'm working on a project in solidjs. For some time now when I click on every button present in my application it does not report. I don't know why because I haven't modified any of my buttons. I'm working on MS Edge, believing it's a browser issue, I re-ran my app on Opera but no success. I also stopped my server then restarted it but nothing. I even shut down my computer and restarted it after a while with no success. So I deleted then reinstalled my node_modules folder but without success. I still face the same problem. I searched the internet for solutions but couldn't find anything about it. I'm working on solid-js version 1.3.3. Thank you for your help !
I am trying to make a react native app with react-native-ble-plx. It works fine on an iOS emulator but crashes on boot when actually put on my iPhone. After some testing, I found that removing the page with the bluetooth stops it from crashing. How do you even go about debugging an error like this, it feels like I can't even get an error if I look for one?
I figured out what I was doing wrong when I couldn't find a crash message. I was building the "release" version instead of the "debug" version in the scheme menu.
It all started when I tried to use the hot reload for storybook, which worked fine on my Macbook, but for whatever reason didn't work on my Windows machine.
I always got a request to __webpack_hmr which would be in the pending-state für about 10 seconds after which it got cancelled and then this cycle would start again.
Since I was running into the same problem with the very basic example from the webpack-hot-middleware GitHub I could rule out storybook.
After a bit of playing around with the example I finally figured out that when using --host=[::1] to start the "server" the hot reload actually started to work. But no luck using anything else like --host=localhost or --host=127.0.0.1.
But I'm still wondering why does the IPv6 host work, but no other configuration? Has anyone run in the same problem before? Why is this problem windows specific and is there anything I can change about my setup?
I am attempting to make my own app with React Native, however it appears as though I'm working harder to get Expo to work more than I am trying to actually debug the app itself. I have tried with LAN, Tunnel, and Local but none of them seems to work. I will get it on some days and it will work fine.. for about 5 minutes and then it will time out or lose connection. Some days though it will just continue to try and load but will never actually pull up the app. I suspect this is because I am using my hotel wifi as well as a vpn (for security on a public network of course). I am wondering if there are any alternatives to expo that I might be able to use because this problem is starting to become very frustrating. Thanks!
You should be able to start Expo in offline mode so that your internet shouldn't be an issue. If you're using yarn the command would be yarn start --offline. You may also need to select Local once Expo launches.
Source: https://github.com/expo/expo-cli/issues/101
Using - Sencha Touch 2.3, Apigee Usergrid JS SDK, and PhoneGap 3.2.
I am able to run my app in the browser and access Apigee perfectly.
index.html:
`<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js"
type="text/javascript"></script>
<script src="../lib/apigee.min.js"></script>
<script type="text/javascript" src="http://maps.google.com/maps/api/js?sensor=true </script>
<!-- The line below must be kept intact for Sencha Command to build your application -->
<script id="microloader" type="text/javascript" src=".sencha/app/microloader/development.js"></script>`
This is my code straight from Apigee Javascript SDK(again in index.html):
`<script type="text/javascript">
var client = new Usergrid.Client({
orgName:'orgname',
appName:'sandbox',
logging: true,
buildCurl: true
});
</script>`
So to test in my view "client.URI" gives me "https://api.usergrid.com" as expected. All good there.
Image here of "client.URI" in a button.
http://minus.com/i/BtmXiuVxljsV
When I run
$ sencha app build -run native
This is where I run into problems. Everything works great except when I try to tie in Apigee. The app does not load in the IOS emulator when I do. In my phonegap config or "whitelist" I have opened up access to everything with the "*" wildcard. I am pretty sure this is working because Google maps API is working great. I tried to put the "client.URI" test in an alert so when I click a button it shows me the URI. Again this works in the browser, but not in the emulator. The app loads fine but when I click on the button nothing happens. I hope this makes sense. I wanted to make sure the app would load and that I could test the "client.URI" test as independently as possible. Again if I try to render it on load then the app never even loads in the emulator.
When I click on the button that should have an alert with the URI I get this in the system.log:
` <Error>: __hid_dispatch_pthread_root_queue_create_block_invoke: specific=0x505c260 pthread_self=0xb0115000`
I could keep developing in the browser and have access to my Usergrid backend, but I would really like to get this bug fixed and make sure I am not dealing with a bigger architectural problem.
Thanks everyone.
One thing that may make a difference is trying to run the emulator from XCode instead of from the command line. Open the .xcodeproj file that Phonegap makes and run from there. If the emulator still doesn't launch, please let us know.
Finally! Thank goodness for nice debugging help from Android. I changed routes and tried it with Android.
It was telling me it couldn't find the Apigee.min.js file. Seems when Phonegap was compiling it either put it in the wrong place or I did to begin with(I'm pretty sure I know which it was)
I changed out my local file to this instead:
<script src="https://apigee.com/usergrid/sdk/usergrid.0.10.5.js"></script>
and it works now on IOS and Android. Was very strange because it worked so well in the browser previously.
If anyone has some feedback on where I went wrong with the putting the file in my app let me know. As you can see above it was in:
<script src="../lib/apigee.min.js"></script>
Also if anyone has recommendations on when deploying if I should keep using Apigee as a source or adding the file to my app.
Thanks everyone for your time.