XRremote throws System Exeption work - 8thwall-xr

8XRremote don't work.
Android app connect to windows via WIFI. And in unity console there is the following log:
C:/Users/Tim/AppData/Local/Android/Sdk/platform-tools/adb threw exception System.Exception: "C:/Users/Tim/AppData/Local/Android/Sdk/platform-tools/adb forward --list" exited with 1
at XRInternal.XREditorBridge+XRRemoteUtils.ExecuteCommand (System.String command, System.String arguments) [0x000d3] in G:\temp\8xr\xr-unity-master\projects\8thWallXR-Demo\Assets\XR\Scripts\XREditorBridge.cs:334
UnityEngine.Debug:LogError(Object)
XRInternal.XRRemoteUtils:ExecuteCommand(String, String) (at Assets/XR/Scripts/XREditorBridge.cs:338)
XRInternal.XRRemoteUtils:ExecuteAdb(String) (at Assets/XR/Scripts/XREditorBridge.cs:303)
XRInternal.XRRemoteUtils:SetupADB() (at Assets/XR/Scripts/XREditorBridge.cs:364)
XRInternal.XREditorBridge:CheckADB() (at Assets/XR/Scripts/XREditorBridge.cs:41)
XRController:Update() (at Assets/XR/Scripts/XRController.cs:984)

The connectivity issue with XR Remote on Windows has been identified and fixed in the newest version of 8th Wall XR (8.1.1.216). The fix is currently on the beta channel. To change channels, you can do the following from the Unity Editor:
Select Assets / XR / 8thWallXR
Select the beta channel from the resulting inspector pane:

Related

ProjectName.iOS Could not register the assembly 'OpenTK-1.0'

I am pretty new in the Xamarin world and I need some help starting the iOS simulator on iPhone X (12.2) or whatever iPhone version.
For example, when I try to start iPhone X (12.2) simulator and start debugging, I get the following error:
ProjectName.iOS[7769:94324] Could not register the assembly 'OpenTK-1.0': System.TypeLoadException: Could not resolve type with token 01000010 from typeref (expected class 'ObjCRuntime.DeprecatedAttribute' in assembly 'Xamarin.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065')
...
Unhandled Exception:
System.ArgumentOutOfRangeException: Token 0x2001513 is not valid in the scope of module Xamarin.iOS.dll
Parameter name: metadataToken
I only started to get this error after I have updated my Mac Mini to 10.14.5 Mojave and updated Xcode to 10.2.1 I have updated Mono on both windows and mac. I have made this update in order to be able to debug on my iPhone which updated to 12.3
The thing is that I can debug on my iPhone 6S with no problem, but when I try to debug on the iPhone simulator, that error pops out.
Currently I am using Visual Studio Professional 15.9.12 (latest version at this time).
Any thoughts?
Thanks!
I have updated my Xamarin Forms, I used version 3.6, I have updated it to version 4.0 and ran a clean and rebuild, the problem solved by itself. I am not sure what exactly caused the problem, but this update seems to have fixed the problem for me.

Xcode 9.3 and Firebase Crashlytics not working

I cannot get Firebase Crashlytics to show my crashes of my Xcode iOS Swift app.
Using Xcode 9.3
I have manually (not using cocoapods) integrated the Crashlytics SDK
as specified here:
https://firebase.google.com/docs/crashlytics/get-started?authuser=0
I have tested both in the simulator and on the device
I made both crash (using an own written crash function, but also the supplied crash function), I restarted the device/simulator (because the crash is only transmitted upon the next launch)
I am not seeing any crashes in the Firebase Crashlytics console, it keeps on saying "Upgrade to Crashlytics for more powerful, realtime crash analysis"
I can confirm in the xcode debug console logs that the crashlytics is running because I see "[Crashlytics] Version 3.10.1 (129)"
I disabled bitcode does not change anything...
I looked in the system console and found:
default 21:17:49.828801 +0200 nsurlsessiond [9
reports.crashlytics.com:443 stream, pid: 72896, traffic class: 200,
tls, indefinite] cancelled
[9.1 463924B9-A95E-44FB-AA19-CFE9616E37E0 192.168.99.209.59507<->54.243.248.96:443]
Connected Path: satisfied (Path is satisfied), interface: en0
Duration: 2.586s, DNS #0.000s took 0.027s, TCP #0.028s took 0.110s, TLS took 0.255s
bytes in/out: 6086/30045, packets in/out: 7/23, rtt: 0.092s, retransmitted packets: 0, out-of-order packets: 0
Its like 9 crashes are pending/hanging? What is this cancelled?
I figured, maybe it's because there are no dsyms uploaded so I checked the build process in Xcode and found:
2018-04-16 21:55:35.270 uploadDSYM[77897:3132594] Fabric.framework/run
1.7.0 (208) 2018-04-16 21:55:35.278 uploadDSYM[77897:3132594] Firebase mode detected. 2018-04-16 21:55:35.278 uploadDSYM[77897:3132594] Using
API Key: "xxxxxxxxxxxxxxxxxx" 2018-04-16 21:55:35.279
uploadDSYM[77897:3132594] Launched uploader in validation mode
What does this "launched uploader in validation mode" mean? Does it mean that the dsym upload is not working?
I wanted to manually upload the dsyms using: https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports?authuser=0 but the fabric.framework does not contain any upload-symbols? The Google documentation wrong? I can see an "uploadDSYM" but this does not seam to have the same options/arguments so I guess it's not this one...?
Based on Todd's input (he is from Crashlytics) I found the issue.
The reason was that the bundleid specified in the Firebase Console for the app was not the one that I was using in the actual app! So I deleted the old app (with the wrong bundle id) and re-created it with the correct bundleid in the Firebase Console and now its working.
Note: it is not possible to change the bundleid once the app is created apparently.

AS3 - iOS app crashes at breakpoint

I have a very annoying problem with debugging AIR apps on iOS devices and simulators.
Simply put, the app crashes when I'm debugging application and it stops at a breakpoint. Then the line with breakpoint is selected for a second or less and then the app is gone.
Here's some logs I got from simulator after last flash trace:
assertiond[30178]: assertion failed: 15G31 13E230: assertiond + 16726 [1BD9E3D0-5485-3412-86B2-4BE50C825E80]: 0x1
SpringBoard[30174]: HW kbd: Failed to set (null) as keyboard focus
SpringBoard[30174]: BSXPCMessage received error for message: Connection invalid
--- last message repeated 1 time ---
com.apple.CoreSimulator.SimDevice.EE317320-40C9-4513-9BE9-02611D6DD722.launchd_sim[30158] (UIKitApplication:com.my.app.id[0x31d1][30651]): Service exited due to signal: Segmentation fault: 11
assertiond[30178]: assertion failed: 15G31 13E230: assertiond + 16726 [1BD9E3D0-5485-3412-86B2-4BE50C825E80]: 0x1
SpringBoard[30174]: Application 'UIKitApplication:com.my.app.id[0x31d1]' crashed.
assertiond[30178]: assertion failed: 15G31 13E230: assertiond + 16726 [1BD9E3D0-5485-3412-86B2-4BE50C825E80]: 0x1
assertiond[30178]: notify_suspend_pid() failed with error 7
And that's it.
The funny thing is that it may not happen for months, then suddenly every breakpoint causes a crash.
From what I've noticed, the device, iOS version, and AIR version don't matter.
Have you guys ever faced this problem? Do you have any solution for this?
The AIR compiler has a known issue in the following scenarios:
If the base class function doesn't use any arguments and the overridden function in the derived class does, then any function calls through the base class reference can cause the application to terminate abruptly.
If 32-bit support is required, downgrading may be required:
However, with the release of AIR 20, only a 64-bit Runtime dynamic Library is provided on Mac OS X. See AIR 20 release notes for details.
Certain users who are running apps that require 32-bit ANEs may want to downgrade to a lower AIR version that supports a 32-bit Runtime dynamic Library.
The Flash Debugger(fdb) combined with the AIR Debug Launcher(ADL) may give more information:
Use the AIR Debug Launcher (ADL) to run both SWF-based and HTML-based applications during development. Using ADL, you can run an application without first packaging and installing it. By default, ADL uses a runtime included with the SDK, which means you do not have to install the runtime separately to use ADL.
AIR supports debugging directly, so you do not need a debug version of the runtime (as you would with Adobe® Flash® Player). To conduct command-line debugging, you use the Flash Debugger and the AIR Debug Launcher (ADL).
The Flash Debugger is distributed in the Flex SDK directory. The native versions, such as fdb.exe on Windows, are in the bin subdirectory. The Java version is in the lib subdirectory. The AIR Debug Launcher, adl.exe, is in the bin directory of your Flex SDK installation. (There is no separate Java version).
Note: You cannot start an AIR application directly with fdb, because fdb attempts to launch it with Flash Player. Instead, let the AIR application connect to a running fdb session.
References
AIR Compiler Known Issues
Building Adobe AIR Applications: AIR Debug Launcher (ADL)
Debugging with fdb
Issues while downgrading from AIR 20 to a lower version on Mac OS X
AIR 20 Release Notes
Archived Adobe AIR SDK versions
Troubleshoot Adobe AIR installation for Mac OS

What is Delphi error code e8000067?

I am building an app using Delphi XE8 and FireMonkey.
I've got it working on Android and am trying to get it working on an iPad.
The iPad is running OS X 5.1.1.
I've got a Debug Provisioning profile.
First, when I tried to run the application on the iPad, I got the error message "Unable to install package. (e8000007)". According to Embarcadero's help page, this was because I was targetting higher versions. So I went to "Project -> Options -> Delphi Compiler -> Linking", found that the minimum target OS was 7.0, and set it to 5.1.1 instead.
Now I'm getting
Unable to launch process <ip address> using the parameters for the <profile name> profile.
The following error was returned: 'Unable to install package. (e8000067)'
This error code is not on the help page. I also don't find it when googling.
Since all these error codes start with "e", it's probably supposed to be a decimal number preceded by "e" for error. Searching for the hexadecimal equivalent of "8000067", i.e. "7A1243", only yields color codes.
I made a "Hello World" app, tried to run it on the iPad, and got the same problem.
What is Delphi error e8000067 ?
It seems that this happens when you're compiling/linking for a 64 bits device, when your device is 32 bits.
When I chose to compile/link for a 32 bit device, the error went away.

iPhone 6 not displaying in IBM Test Workbench Mobile Devices Tab

Tool: IBM Mobilefirst TestWorkbench 8.6.0.1
OS: Windows 7
Device: iPhone 6 Version: 8.1.2
Laptop and iPhone are on same Network.
Click on Add Devices icon in Mobile Devices tab. Test Workbench URL pops up.
Entered the URL in my Safari browser in iPhone.
IBM Rational Test Workbench Mobile Client opens in my browser.
Problem
The Device does not show up in Mobile Devices Tab.
Able to record a Test in my iPhone6. After recording, getting a pop up in Test Workbench which says "Click here to generate Test Recordings". When i click that i get the below error in Error log
Plug-in: com.ibm.rational.test.lt.recorder.moeb
Message: CRRTWM1201E Unexpected exception while performing test generation.
Exception Stack Trace:
java.io.IOException: Unable to access device used for recording.
at com.ibm.rational.test.lt.recorder.moeb.ui.wizards.CreateTestFromRecordingLogsWizard.getSessionProducer(CreateTestFromRecordingLogsWizard.java:150)
at com.ibm.rational.test.lt.recorder.moeb.ui.wizards.CreateTestFromRecordingLogsWizard.createRecordingSession(CreateTestFromRecordingLogsWizard.java:128)
at com.ibm.rational.test.lt.recorder.moeb.ui.wizards.CreateTestFromRecordingLogsWizard.access$0(CreateTestFromRecordingLogsWizard.java:125)
at com.ibm.rational.test.lt.recorder.moeb.ui.wizards.CreateTestFromRecordingLogsWizard$1.run(CreateTestFromRecordingLogsWizard.java:91)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at com.ibm.rational.test.lt.recorder.moeb.ui.wizards.CreateTestFromRecordingLogsWizard.performFinish(CreateTestFromRecordingLogsWizard.java:86)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
Problem Guesses: Had instrumented the iOS app in Mac with jdk1.6
Presently uploaded the instrumented iOS app in Test Workbench in Windows Laptop which has jdk1.7. Could this be the problem ?
No the jdk should not be the issue.
The fact that your device doesn't appear in the mobile devices tab is not normal. This seems to be the origin of the issue.
The version 8.6.0.1 seems to be old... I recommand first that you update to the last one (8.7), re-instrumente the app and try again please ?
Thanks
Dominique

Resources