I am trying to track my iPhone using traccar.
I installed traccar server in windows 7 and ios client application in iphone 4s.
I added my iPhone successfully in traccar web application and it is updating location per minute.
But in traccar we application when I load my phone it always display error "No results found for selected period"
Below is a log file of traccar server...
2015-01-27 11:59:44
INFO: Starting server... 2015-01-27 11:59:44 INFO: Operating
System name: Windows 7 version: 6.1 architecture: x86 2015-01-27
11:59:44 INFO: Java Runtime name: Java HotSpot(TM) Client VM vendor:
Oracle Corporation version: 25.31-b07 2015-01-27 11:59:44 INFO:
Memory Limit heap: 247mb non-heap: 0mb 2015-01-27 11:59:44 INFO:
Version: 2.11-SNAPSHOT 2015-01-27 12:02:39 DEBUG: [5005 <-
192.168.1.59] - HEX: 24504749442c3838353839352a30300d0a 2015-01-27 12:02:39 WARN: Unknown device - 885895 2015-01-27 12:02:42 DEBUG:
[5005 <- 192.168.1.59] - HEX:
244750524d432c3036333231342e3030302c412c323833362e383730352c4e2c30373732312e373135302c452c302e30302c3131362e30322c3237303131352c2c2a30300d0a
2015-01-27 12:03:46 DEBUG: [5005 <- 192.168.1.59] - HEX:
244750524d432c3036333331352e3030302c412c323833362e383731362c4e2c30373732312e373134322c452c302e30302c302e30302c3237303131352c2c2a30300d0a
Please provide appropriate solution.
You need to register your device through web interface with 885895 as a unique identifier.
I had the same problem because I was trying this application in my office. You know that GPS doesn't work indoors so you will have to go outside with your Iphone. Try it if work.
Best of luck!
Related
I had an iOS iPad app crash and got the following crash log from the Devices tab:
Date/Time: 2017-10-13 15:06:22 -0600
OS Version: iPhone OS 11.1 (Build 15B5066f)
Architecture: arm64
Report Version: 26
Data Source: KPerf Lightweight PET
Kernel Cache: 0xffffffe000000000 1C4A9D92-74B9-1F20-096E-27915D7A6C03
Reason: Fence-hang-Vocab: 505ms handling fence, blown-fence (fence duration=505ms)
Command: Vocab
Path: /private/var/containers/Bundle/Application/9F4A7C15-D23E-46C8-B724-84C57D83B455/Vocab.app/Vocab
Identifier: com.mycompany.Vocab
Version: 1.4.0 (420)
Parent: debugserver [1467]
PID: 1469
Duration: 0.55s
Steps: 11 (50ms sampling interval)
Hardware model: J71AP
Active cpus: 2
Any insight into what this error is and what causes it?
According to this Apple Developer Forums Thread, one cause of blown fence errors is due to high memory pressure.
The developer of the app in question might be able to monitor memory pressure of the app, which could be a cause for the app being terminated.
Updated my xcode this evening to 7.2.1 im running on yosemite 10.10.5
i've just started learning swift, and everytime i try to run the simulator it crashes with the error:
could not load inserted library '/usr/lib/libignitor2.dylib' because no suitable image found.
I have spent the last 4 hours searching online, there seems to be a few similar errors of inserted library missing but nothing that i can see that helps with this error. The full code can be seen below.
Process: Simulator [2907]
Path: /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator
Identifier: com.apple.iphonesimulator
Version: 9.2 (643)
Build Info: Indigo-643000000000000~28
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Simulator [2907]
User ID: 501
Date/Time: 2016-09-10 03:00:48.102 +0100
OS Version: Mac OS X 10.10.5 (14F1912)
Report Version: 11
Anonymous UUID: 1ACB9325-E877-4FA4-FEBD-B9450D15E13A
Time Awake Since Boot: 10000 seconds
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
DYLD_INSERT_LIBRARIES=/usr/lib/libignitor2.dylib
Dyld Error Message:
could not load inserted library '/usr/lib/libignitor2.dylib' because no suitable image found. Did find:
/usr/lib/libignitor2.dylib: mmap() error 1 at address=0x107DE9000, size=0x00001000 segment=__TEXT in Segment::map() mapping /usr/lib/libignitor2.dylib
Binary Images:
0x107da0000 - 0x107dccff7 com.apple.iphonesimulator (9.2 - 643) <2A577F90-517C-3363-A980-EEB79D21FEBF> /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator
0x7fff65635000 - 0x7fff6566b92f dyld (353.2.4) <708E385E-50C6-32A3-983C-42E97BEE4346> /usr/lib/dyld
Model: MacBookPro12,1, BootROM MBP121.0167.B14, 2 processors, Intel Core i5, 2.7 GHz, 16 GB, SMC 2.28f7
Graphics: Intel Iris Graphics 6100, Intel Iris Graphics 6100, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1867 MHz, 0x02FE, 0x4544464232333241314D412D4A442D460000
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1867 MHz, 0x02FE, 0x4544464232333241314D412D4A442D460000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.15.166.24.3)
Bluetooth: Version 4.3.6f3 16238, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0128G, 121.33 GB
USB Device: Internal Memory Card Reader
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1
Any help would be appreciated. thanks
You could try
sudo update_dyld_shared_cache -force
I'm trying to fix my beta but it appears to be trying to get after an update and this is the solution I"m working with. If it fails you can try
https://apple.stackexchange.com/questions/217232/trying-to-force-update-dyld-shared-cache-but-having-some-errors
I hope this is helpful
When Appium tries to run application, the screen flashes with app splash screen, as if Appium tries to launch app multiple times. This behaviour happens both on simulator and real device.
I set enable on my iOS devices UI Automation, but when I try start inspector I have this problem:
info: [debug] [INST STDERR] 2015-11-05 15:11:05.082 instruments[1495:39489] WebKit Threading Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] 2015-11-05 15:11:06.049 instruments[1495:39460] Attempting to change event horizon while disengage
error: Failed to start an Appium session, err was: Error: Instruments crashed on startup
info: [debug] [INST STDERR] 2015-11-05 15:11:06.049 instruments[1495:39462] Attempting to change event horizon while disengage
Instruments Trace Error : Target failed to run: Permission to debug com.myapp.iphone was denied. The app must be signed with a development identity (e.g. iOS Developer).
info: [IOS_SYSLOG_ROW ] Nov 5 15:11:04 tests-iPod com.apple.xpc.launchd[1] (UIKitApplication:com.myapp.iphone[0xe163][607]) <Notice>: Service exited due to signal: Killed: 9
info: [debug] [INSTSERVER] Instruments exited with code 253
info: [debug] Killall instruments
info: [debug] Instruments crashed on startup
info: [debug] We exceeded the number of retries allowed for instruments to successfully start; failing launch
info: [debug] Stopping iOS log capture
info: [debug] Reset not set, not ending sim or cleaning up app state
info: [debug] Cleaning up appium session
info: [debug] Error: Instruments crashed on startup
at [object Object].Instruments.onInstrumentsExit (/Applications/Appium.app/Contents/Resources/node_modules/appium/submodules/appium-instruments/lib/instruments.js:440:31)
at [object Object].<anonymous> (/Applications/Appium.app/Contents/Resources/node_modules/appium/submodules/appium-instruments/lib/instruments.js:353:12)
at ChildProcess.emit (events.js:110:17)
at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Instruments crashed on startup)","origValue":"Instruments crashed on startup"},"sessionId":null
info: <-- POST /wd/hub/session 500 33841.937 ms - 182}
Application is in form of .ipa
Target failed to run: Permission to debug com.myapp.iphone was denied.
The app must be signed with a development identity (e.g. iOS Developer).
You application should be signed with developers key. Click here for documentation
If you are using iOS Simulator, do the following...
In Appium, go to Developer Settings, Check Custome Server Flags and write --native-instruments-lib in the text box.
Now start Appium Server.
Hope this helps!
BlockquoteTarget failed to run: Permission to debug com.myapp.iphone was denied.
The app must be signed with a development identity (e.g. iOS Developer).
Blockquote
You should give your developer identity while creating the .ipa...
If you are creating ipa file through terminal, you can follow the given link [blog]: Xcode "Build and Archive" from command line
I also struggled with this problem and found that you need to enable UI automation in developer option in you iDevice
How to enable UI Automation
1. switch off the iDevice,
2. then connect it to the Mac running Xcode
3. before switching it back on to have Developer options appear.
4. tap on developer option and Enable UI automation
In my case, the following command made my life hell:
rm -rf $HOME/Library/Developer/Xcode/iOS\ DeviceSupport/*
So don't add it to the build step.
To fix the issue:
Restart device > run Xcode > connect device > build & run the app > stop & quit Xcode
Now verify launching app without crashing the instruments.
I want to run automation test on real devices, earlier i did this on emulators (API>17) but the same test i was trying to run on Appium in selendroid mode it failed.
Below is the capabilities i configured for appium to run in selendroid mode.
Appium Version : 1.0
Selendroid Version: 0.10
I run appium on port no : 6001 and bootstrap port : 4001, And selendroid server run on default port : 8080
private static String url = "http://localhost:"
+ System.getProperty("appium_port") + "/wd/hub";
private AppiumDriver driver;
private static DesiredCapabilities capabilities;
capabilities = new DesiredCapabilities();
File app = new File("en-android.apk");
capabilities.setCapability(CapabilityType.BROWSER_NAME, "Selendroid");
capabilities.setCapability(CapabilityType.PLATFORM, "ANDROID");
capabilities.setCapability("device", "Selendroid");
capabilities.setCapability("platformVersion", "4.1.2");
capabilities.setCapability("app", app.getAbsolutePath());
capabilities.setCapability("app-activity",
"testapp.android.gui.WelcomeActivity");
capabilities.setCapability("app-package",
"testapp.android");
driver = new AppiumDriver(new URL(url), capabilities);
Below is Applium server logs.
Appium Log:
error: Android devices must be of API level 17 or higher. Please change your device to Selendroid or upgrade Android on your device.
info: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
info: Sent shutdown command, waiting for UiAutomator to stop...
warn: UiAutomator did not shut down fast enough, calling it gone
info: Cleaning up android objects
info: Cleaning up appium session
error: Failed to start an Appium session, err was: Error: Android devices must be of API level 17 or higher. Please change your device to Selendroid or upgrade Android on your device.
info: Error: Android devices must be of API level 17 or higher. Please change your device to Selendroid or upgrade Android on your device.
at /home/priyankpshah/.linuxbrew/lib/node_modules/appium/lib/devices/android/android.js:263:17
at /home/priyankpshah/.linuxbrew/lib/node_modules/appium/lib/devices/android/adb.js:630:7
at /home/priyankpshah/.linuxbrew/lib/node_modules/appium/lib/devices/android/adb.js:154:5
at ChildProcess.exithandler (child_process.js:635:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Socket.<anonymous> (child_process.js:956:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:465:12)
info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Android devices must be of API level 17 or higher. Please change your device to Selendroid or upgrade Android on your device.)","origValue":"Android devices must be of API level 17 or higher. Please change your device to Selendroid or upgrade Android on your device."},"sessionId":null}
POST /wd/hub/session 500 7269ms - 400b
Tests run: 4, Failures: 1, Errors: 0, Skipped: 3, Time elapsed: 8.198 sec <<< FAILURE! - in TestSuite
setUp(com.ishisystems.enigma.EnigmaLaunchTest) Time elapsed: 8.084 sec <<< FAILURE!
org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: Android devices must be of API level 17 or higher. Please change your device to Selendroid or upgrade Android on your device.) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 7.41 seconds
Build info: version: '2.41.0', revision: '3192d8a6c4449dc285928ba024779344f5423c58', time: '2014-03-27 11:29:39'
System info: host: 'ishiahm-lt113', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-24-generic', java.version: '1.7.0_55'
Driver info: io.appium.java_client.AppiumDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:193)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:595)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:76)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:153)
at io.appium.java_client.AppiumDriver.<init>(AppiumDriver.java:41)
at TestUtility.automationInit(TestUtility.java:41)
at LaunchTest.setUp(LaunchTest.java:33)
Please let me know is there any specific changes need to be made to run appium tests on selendroid mode on real devices.
Thanks,
Priyank P Shah
If you are using Appium 1.0 use capability 'automationName' instead of device.
E.G.
capabilities.setCapability("automationName", "Selendroid");
instead of
capabilities.setCapability("device", "Selendroid");
For appium versions less than 1.0 beta , you can continue with 'device' capability.
I'm trying to install 64-bit drivers using DPInst.exe and Inno Setup. When I execute the installer, DPInst is launched and then displays the error "DPInst.exe does not execute on your current Operating System". This made me think that I grabbed the 32-bit version instead of the 64-bit version of DPInst.exe, but if I wait until the installer is done I can then run the DPInst manually and it executes just fine and installs the drivers.
Here is the relevant portion of my Inno Setup script:
[Files]
Source: "...DPInst.exe"; DestDir: {app}\Drivers; Flags: ignoreversion
[Run]
Filename: {app}\Drivers\DPInst.exe; WorkingDir: {app}\Drivers;
This seems pretty straightforward, so I don't know what I'm missing here. It works if I run it outside Inno Setup, so I'm not sure why I get an error about my current OS when it runs inside Inno Setup.
Any ideas?
UPDATE: Over the weekend, the machine performed a Windows update and Win 7 SP1 was installed. Now the DPInst when called from Inno Setup works. I then re-imaged the machine back to pre-SP1 and it again failed. I checked the DPINST.log and found this:
INFO: ****************************************
INFO: 11/25/2013 13:43:54
INFO: Product Version 2.1.0.0.
INFO: Version: 6.1.7600
INFO: Platform ID: 2 (NT)
INFO: Service Pack: 0.0
INFO: Suite: 0x0100, Product Type: 1
INFO: Architecture: AMD64.
INFO: Interactive Windows Station
INFO: Command Line: '"D:\Program Files\Digital Audio Corporation\MicroDAC 5\Drivers\DPInst.exe"'
INFO: DPInst is not multi-lingual.
INFO: ****************************************
INFO: Current working directory: 'D:\Program Files\Digital Audio Corporation\MicroDAC 5\Drivers'
INFO: Running on path 'D:\Program Files\Digital Audio Corporation\MicroDAC 5\Drivers'
INFO: No valid 'dpinst.xml' file provided.
ERROR: DPInst.exe not supported on current OS.
INFO: Returning with code 0x80000000
INFO: 11/25/2013 13:43:56
INFO: ****************************************
INFO: 11/25/2013 13:44:42
INFO: Product Version 2.1.0.0.
INFO: Version: 6.0.6000
INFO: Platform ID: 2 (NT)
INFO: Service Pack: 0.0
INFO: Suite: 0x0100, Product Type: 1
INFO: Architecture: AMD64.
INFO: Interactive Windows Station
INFO: Command Line: '"D:\Program Files\Digital Audio Corporation\MicroDAC 5\Drivers\DPInst.exe" '
INFO: DPInst is not multi-lingual.
INFO: ****************************************
INFO: Current working directory: 'D:\Program Files\Digital Audio Corporation\MicroDAC 5\Drivers'
INFO: Running on path 'D:\Program Files\Digital Audio Corporation\MicroDAC 5\Drivers'
INFO: No valid 'dpinst.xml' file provided.
INFO: Wizard cancelled by user on welcome page.
INFO: Returning with code 0x80000000
INFO: 11/25/2013 13:44:44
Notice the Version field goes from 6.1.7600 to 6.0.6000. The first run is from Inno Setup when it failed (notice ERROR) and the second run is when I run it manually. What does the "Version" field represent? And why would SP1 being installed make a difference?
Thanks,
Jason