I'm trying to get the user's current position using forge.geolocation.getCurrentPosition. I have the module enabled in my code, I have my device's GPS and mobile data turned on, and I'm running the code on my Android device from Trigger Toolkit.
When I do this, it appears that forge.geolocation.getCurrentPosition never executes. Neither the success or fail callback function are reached (the first command in each is a log message). Nor are any errors thrown.
However, when I package my app as an apk and install it on my device, the exact same code works just fine.
Any ideas why this isn't executing on Android via Trigger Toolkit, or how I can go about debugging this?
Related
While developping an app for an iPad on my Mac, I use print logs to monitor what is going on (regular prints in Swift code). However I really don't like the Xcode console, and I'd like to be able to redirect the stream to a file, where I can then read it with a better log viewer (and add color!).
I'm executing the app in debug mode through Wifi on my iPad, but I want the logs on my Mac, so storing the logs to a file on the device is not really interesting (SO question here). Wrapping the debugger executable seems interesting, as suggested here but I couldn't find anything more recent (with lldb).
Alternatively, I could also run the debugger from the console and handler the redirection from there, but I don't know how to do that for debugging on a remote device over WiFi.
Any help would be greatly appreciated!
While testing a release build of our React Native app on iOS, we discovered a defect with an input component that only occurred after the app had been in the background for a longer time (e.g. 1h). Presumably, this occurs after the app has been suspended by the OS.
I'm now trying to debug this issue, but when I run the app on a test device in debug mode and connected to the React Native Debugger, turn the screen off for some time and then bring the app back to the foreground, it will show a red screen with Runtime is not ready for debugging. error. This does not happen when I immediately bring the app back to the foreground after turning the screen off, so I suppose it's also related the app being suspended.
We're using React 16.3.0 and React Native 0.54.0 (preparing an update in a separate branch).
Can anyone help me understand what's going on here, and provide a suggestion on how to debug this issue?
Could you use something like Sentry for bug reporting? Not only does it log JavaScript errors, but native crashes too. This is great for seeing continuous errors encountered by your users, whilst in production.
You could also run a production build and debug it via USB.
Navigate to Product > Scheme > Edit Scheme. Ensure you've selected Production in the Build Configuration. Also select Debug Executable.
Once the application launches, go to View > Debug Area > Activate Console. You should now see any native logs from your app.
Can't really help with the problem that you're facing but you should take a look at Reactotron for debugging in react-native.
I'm working on test automation that uses appium for it's connection to an android device. Occasionally, I end up in a spot where I'm debugging why a test has failed, and it is because a developer has changed something so my id no longer works, or the xpath has changed, or some other weirdness where a developer changed something and didn't consider the tester (like that's never happened).
I would like to be able to run my automation, and right before the query runs, hit a breakpoint, and then I start the appium inspector and look at the page from there. It takes a long time for me to stop debugging, restart appium, then manually execute the test case to get me back into the same position I was in while debugging just to be able to see what the debug id's are on the app.
Is there a way to achieve this?
the best way is to unplug and plug yet your device, then run uiautomatorviewer.exe in order to inspect the current view..
I have trouble determining why my iOS emulator is not updating in real time as I update my code. Each time I make changes, the terminal registers the updates, however the emulator doesn't refresh the view. This is my console output:
Compilation complete. Watching for files changes.
File Change detected. Starting incremental compilation...
Compilation complete. Watching for file changes.
If anybody could please point me in the direction of this issue, that would be superb as there isn't much else to go by on any other forums.
I found that when running the application from a file path which contained a space, the real time updates had trouble. After ensuring all directories within the project absolute path contained no spaces, the livereload worked.
You need to be more clear on what you did to "not work".
Here's how I do it to make things livereload.
tns run ios
If I do above without a device plugged in, it automatically uses the Emulator. If I have a device plugged in, it uses the device.
Livereload works for both instances, such as when I add things to the template.
We are attempting to activate Mono for Android. After loading version monoandroid-1.0.0.10192, which does not ask for the activation code by the way, running a project in Visual Studio 2010 works as expected. But when you attempt to run the project it is still in evaluation mode and will not allow downloads to devices.
Clicking 'Click to activate' works properly.
A window pops up asking for information. After entering all necessary information (with activation code), the activate button runs a program called, mandroid.exe, in the task manager -- some kind of command line program.
It runs for about 3 seconds and does nothing. No status report or anything.
Activation is impossible.
Has anyone experienced this before?
You activate it on the Window that comes up asking you to select an emulator, there is a small link that says "Click here to activate". The reason it is placed there, albeit very difficult to find is because the Trial version is ONLY limited by being able to not deploy to a physical device.
To get there:
1. Close all emulators
2. Run Application
3. Dialog will appear
4. Click Link to Activate
Hope that helps!