I want to integrate YouTubeAndroidPlayerApi_1.2.2 in my app. But when I use this sdk, I found a exception:
* AndroidRuntime: FATAL EXCEPTION: main
* AndroidRuntime: Process: com.google.android.youtube.player, PID: 22244
* AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method 'void abzx.a()' on a null object reference
* AndroidRuntime: at abtv.e(SourceFile:193)
* AndroidRuntime: at com.google.android.apps.youtube.embeddedplayer.service.service.jar.RemoteSurfaceMediaView.surfaceDestroyed(SourceFile:22)
* AndroidRuntime: at com.google.android.apps.youtube.embeddedplayer.service.service.jar.RemoteSurfaceHolder.a(SourceFile:23)
* AndroidRuntime: at com.google.android.apps.youtube.embeddedplayer.service.service.jar.ApiPlayerService.c(SourceFile:202)
* AndroidRuntime: at com.google.android.apps.youtube.embeddedplayer.service.service.jar.ApiPlayerService$13.run(SourceFile:3)
* AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:815)
* AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:104)
* AndroidRuntime: at android.os.Looper.loop(Looper.java:207)
* AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5845)
* AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
* AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1029)
* AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:878)
If anyone knows how to resolve this problem, please tell me. Thanks!
The YouTube Player API has many obscure issues. To avoid such problems I have built an open source player that can be used as an alternative to the official player. You won't have this kind of issues using it: android-youtube-player.
Related
The application crashed when I run it.
The debug console result:
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x108597170 UIView:0x10857e6e0.trailingMargin == UIButton:0x10b50fa60'Filters'.trailing + 8 (active)>
Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in may also be helpful.
2018-10-09 11:13:05.328331+0800 KAppLocator[438:86468] TIC Read Status [1:0x0]: 1:57
2018-10-09 11:13:05.349980+0800 KAppLocator[438:86468] TIC Read Status [1:0x0]: 1:57
2018-10-09 11:13:07.929435+0800 KAppLocator[438:86324] * Terminating app due to uncaught exception 'NonExistentDocumentException', reason: 'Document '' doesn't exist. Check document.exists to make sure the document exists before calling document.data.'
* First throw call stack:
(0x18101ed8c 0x1801d85ec 0x100b916e8 0x100a3c460 0x100a3df74 0x100a3e01c 0x100b909dc 0x100b90ff4 0x1035f91dc 0x1035f919c 0x1035fdd2c 0x180fc7070 0x180fc4bc8 0x180ee4da8 0x182eca020 0x18af04758 0x100ad8324 0x180975fc0)
libc++abi.dylib: terminating with uncaught exception of type NSException
I've check the FSTDocumentsKey and the users/zdfWJ3sv2JXgYu8iXsA0tGI1CYF2> and the documents key exists in firebase.
Found out also the error, Thread 1 signal SIGBART [FIRDocumentSnapshot data]
What is the possible cause of crashing?
Thank you in advance, folks! :)
I'm making an app with Swift and Firestore and since yesterday evening, my app crash when it start on when executing :
FirebaseApp.configure()
Here is the error message :
2018-05-23 10:27:08.562176+0200 protoMeteoApp[51741:3501027] 4.9.0 - [Firebase/Analytics][I-ACS023007] Firebase Analytics v.40009000 started
2018-05-23 10:27:08.578312+0200 protoMeteoApp[51741:3501027] 4.9.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see https://help.apple.com/xcode/mac/8.0/#/dev3ec8a1cb4)
2018-05-23 10:27:08.592866+0200 protoMeteoApp[51741:3500914] * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[3]'
First throw call stack:
(
0 CoreFoundation 0x000000010925f1e6
__exceptionPreprocess + 294
......
)
libc++abi.dylib: terminating with uncaught exception of type NSException
I tried to fix it creating a new project, downloading again "GoogleService-Info.plist" but it still crash.
Any idea ?
Can add following two keys into your Info.plist file:
Set FirebaseAppDelegateProxyEnabled to YES
Set FirebaseScreenReportingEnabled to NO
Also configure your Firebase app into AppDelegate.swift file inside didFinishLaunchingWithOptions method before use of Firebase as:
FirebaseApp.configure()
I am getting this error:
System.NullReferenceException: Object reference not set to an instance
of an object
at MonoTouch.Design.Client.IPhoneDesignerSession +
<MaybeConvertToLatestXcode>c__async5.MoveNext () [0x0004c] in
/Users/builder/data/lanes/4470/6c2f6737/source/md-
addins/Xamarin.Designer.iOS/MonoTouch.Design.Client/
IPhoneDesignerSession.cs:774
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw ()
[0x0000c] in /private/tmp/source-mono-d15-3/bockbuild-d15-
3/profiles/mono-mac-xamarin/build-root/mono-
x64/mcs/class/referencesource/mscorlib/system/runtime/
exceptionservices/exceptionservicescommon.cs:151
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
(System.Threading.Tasks.Task task) [0x00037] in /private/tmp/source-
mono-d15-3/bockbuild-d15-3/profiles/mono-mac-xamarin/build-root/mono-
x64/mcs/class/referencesource/mscorlib/system/runtime/compilerservices/
TaskAwaiter.cs:187
I cannot view my storyboard.
I think it better to address this issue to xamarin support.
For now, you can try to open your storyboard in XCode.
I'm currently trying to run on Xcode an app I ve made with Qt, but when I try to run it on Xcode i get this Exception :
dyld: warning, Ignoring DYLD_IMAGE_SUFFIX because DYLD_ROOT_PATH is used.
2016-10-10 15:37:04.777 CMP[2206:654538] *** Assertion failure in void _UIApplicationMainPreparations(int, char **, NSString *__strong, NSString *__strong)(), /BuildRoot/Library/Caches/com.apple.xbs/Sources/UIKit_Sim/UIKit-3512.60.7/UIApplication.m:3702
2016-10-10 15:37:04.783 CMP[2206:654538] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Unable to instantiate the UIApplication subclass instance. No class named NSApplication is loaded.'
*** First throw call stack:
(
0 CoreFoundation 0x06a27494 __exceptionPreprocess + 180
1 libobjc.A.dylib 0x07c4fe02 objc_exception_throw + 50
2 CoreFoundation 0x06a2732a +[NSException raise:format:arguments:] + 138
3 Foundation 0x05eba390 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 102
4 UIKit 0x04703177 _UIApplicationMainPreparations + 645
5 UIKit 0x04702e73 UIApplicationMain + 90
6 CMP 0x0004f6f6 qt_main_wrapper + 678
7 libdyld.dylib 0x0b53fa25 start + 1
8 ??? 0x00000001 0x0 + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
anyone can help please ?
In your app's info.plist, make sure you change the NSPrincipalClass key to the name of your subclass. This'll make Cocoa instantiate the correct class when the applications loads - you shouldn't have to do anything other than that to get your subclass working. Also, take a look at this link it may also add some insights to your question. Demystifying NSApplication
If your application startup is instantiated programmatically & you hit this problem, see if there's an NSPrincipalClass key in your Info.plist. If there is, remove it & see what happens.
Trying to add Simperium to my existing app, I get a NSAssertion error:
(gdb) po $eax
Simperium couldn't load member data (unsupported type)
Stack trace:
(gdb) bt
#0 0x02f63cbc in objc_exception_throw ()
#1 0x0190da48 in +[NSException raise:format:arguments:] ()
#2 0x00a5b2cb in -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] ()
#3 0x003ac625 in -[SPCoreDataExporter addMembersFrom:to:] (self=<value temporarily unavailable, due to optimizations>, entityDesc=<value temporarily unavailable, due to optimizations>) at /Users/kineticpoet/dev/simperium-ios-private/Simperium/SPCoreDataExporter.m:95
#4 0x003acd3b in -[SPCoreDataExporter exportModel:classMappings:] (_cmd=0x3fa641, model=0x7b377560) at /Users/kineticpoet/dev/simperium-ios-private/Simperium/SPCoreDataExporter.m:156
#5 0x00374a4d in -[Simperium startWithAppID:APIKey:model:context:coordinator:] (self=<value temporarily unavailable, due to optimizations>, _cmd=<value temporarily unavailable, due to optimizations>, model=<value temporarily unavailable, due to optimizations>) at /Users/kineticpoet/dev/simperium-ios-private/Simperium/Simperium.m:385
#6 …
What are the supported types? Are binary data supported? My app uses "Allows external storage" for binary data. Is that supported?
How can I find out more info?
UPDATE:
Extending Simperiums Simpletodo example and adding a new entity with binary data attribute leads to the same error:
…
2012-05-13 14:30:20:192 SimpletodoFinal[42429:fb03] Simperium starting...
2012-05-13 14:30:20.222 SimpletodoFinal[42429:fb03] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Simperium couldn't load member data (unsupported type)'
*** First throw call stack:
(0x17f2022 0x1bcecd6 0x179aa48 0xdda2cb 0x3fb85 0x4029b 0x7fad 0x2e37 0x441386 0x442274 0x451183 0x451c38 0x445634 0x2082ef5 0x17c6195 0x172aff2 0x17298da 0x1728d84 0x1728c9b 0x441c65 0x443626 0x290d 0x2875 0x1)
terminate called throwing an exception
Update^2:
Simperium starts sync after changing superclass of entity with binary data to non NSManagedObject class.
Simperium's support for the binary type in Core Data is currently undocumented and limited. To prevent Simperium from seeing any particular attribute (including binary attributes, which aren't yet fully supported), you can add a User Info parameter to that attribute.
Highlight the attribute in the model editor, open the inspector pane, and add a User Info parameter. Set the key to spDisableSync and the value to 1. This should allow the rest of that entity to be used successfully with Simperium (if you need it).