HLS local http server on iOS8 doesn't work - http-live-streaming

I'm creating a local http server to provide http live streaming to a AVPlayer. It works fine on iOS 7, but failed in iOS 8 beta. Player never send request to my local server, its playerItem's status always become AVPlayerStatusFailed right after I call player's 'play' method.
The error I received is as following:
Error Domain=AVFoundationErrorDomain Code=-11800 "The operation could not be completed" UserInfo=0x179c675c0 {NSUnderlyingError=0x17a252c60 "The operation couldn’t be completed. (OSStatus error -12666.)", NSLocalizedFailureReason=An unknown error occurred (-12666), NSLocalizedDescription=The operation could not be completed}
I have asked this issue on iOS Developer forum and got response from Apple - "it's due to a bug in the first 8.0 seed".
However, they didn't say that they'll fix this bug and instead asking me why I need to do this. Does anyone have the same problem?

Related

"Error: Internal error encountered" while running RequestSync to Google Homegraph API - Node.js

I am using a Nodejs client to integrate with Google Smart Home.
When I request to RequestSync API, it sometimes shows the following error.
Error: Internal error encountered.
Although I saw the above error, it seems that the SYNC request has been triggered properly.
Does anyone know why this happens?
Since the request failed and returned an error, our app retries the RequestSync again and again, so I'd like to fix the error if possible.
Thank you.
Environment
#googleapis/homegraph: 3.0.2
Nodejs: 18.4.0

CodeCollaborator client fails to add files to review

I am trying to submit a code review request using CodeCollaborator client v7.2.7237 (server version is same too) but fails with the following error call stack –
com.smartbear.ccollab.datamodel.DataModelException: org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Read timed out
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$2.invoke(XmlRpcClientEngineImplementation.java:355)
at com.sun.proxy.$Proxy63.loadById(Unknown Source)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation.loadById(XmlRpcClientEngineImplementation.java:441)
at com.smartbear.ccollab.datamodel.Engine$DataObjectCache.loadObjectById(Engine.java:6691)
at com.smartbear.ccollab.datamodel.Engine.loadById(Engine.java:537)
at com.smartbear.ccollab.datamodel.Engine.loadEngineObjectById(Engine.java:564)
at com.smartbear.ccollab.datamodel.Engine.versionCreate(Engine.java:5913)
at com.smartbear.ccollab.datamodel.Scm.uploadScmVersion(Scm.java:629)
at com.smartbear.ccollab.datamodel.Scm.uploadChangeset(Scm.java:448)
at com.smartbear.ccollab.datamodel.Scm.uploadChangeset(Scm.java:392)
at com.smartbear.ccollab.datamodel.Scm.uploadChangelist(Scm.java:291)
at com.smartbear.ccollab.client.commands.AbstractAddChangelistCommand.execute(AbstractAddChangelistCommand.java:139)
at com.smartbear.ccollab.client.commands.admin.review.AbstractReviewCommand.execute(AbstractReviewCommand.java:125)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:345)
at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:419)
at com.smartbear.collaborator.Collaborator.execute(Collaborator.java:160)
at com.smartbear.collaborator.jobs.AddToReviewJob.processChanges(AddToReviewJob.java:158)
at com.smartbear.collaborator.jobs.AddToReviewJob.run(AddToReviewJob.java:103)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Read timed out
at org.apache.xmlrpc.client.XmlRpcCommonsTransport.writeRequest(XmlRpcCommonsTransport.java:252)
at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:151)
at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:115)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientFactory$XmlRpcCommonsTransport2.sendRequest(XmlRpcClientFactory.java:75)
at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158)
at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147)
at com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$2.invoke(XmlRpcClientEngineImplementation.java:256)
... 18 more
I have no problems accessing Perforce or CodeCollaborator from the machine when I get this error. I tried to submit using CodeCollaborator plugin in P4V (P4V/NTX64/2019.1/1797168) but got the same error message. I tried JRE 1.6, 1.7 but got the same error.
When I login to my CodeCollaborator account, I see that review request is being created but it is failing to add the source files to the review. My colleagues with the same CodeCollaborator, P4 versions are successfully able to submit the review requests. Checked this thread on CodeCollaborator forum who had reported similar issue but there was no solution to try. Any suggestions on how to troubleshoot ? Thanks.

Xamarin.Android & Azure Push Notifications Internal Server Error

I'm following the guide at https://learn.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-xamarin-android-get-started-push (as well as the original Xamarin one that this appears to have cribbed from), but I'm running into a problem registering my client.
I am successfully logging a user in prior to setting up the push notification service.
Both GcmClient.CheckDevice(...) and GcmClient.CheckManifest(...) succeed, and my PushHandlerService is being called.
Push.RegisterAsync(...) in my PushHandlerService is throwing a MobileServiceInvalidOperationException because it received an HTTP 500 Internal Server Error from the service.
Looking at FREB logs, it appears that the "error" is actually supposed to be a success, and interestingly is somehow related to the EasyAuthModule:
NOTIFY_MODULE_COMPLETION ModuleName="EasyAuthModule_64bit", Notification="AUTHENTICATE_REQUEST", fIsPostNotificationEvent="true", CompletionBytes="297", ErrorCode="The operation completed successfully.
(0x0)" 05:51:01.092
Module_set_response_error_status
Warning ModuleName="EasyAuthModule_64bit", Notification="AUTHENTICATE_REQUEST", HttpStatus="500", HttpReason="Internal Server Error", HttpSubStatus="79", ErrorCode="Unspecified error
(0x80004005)", ConfigExceptionInfo="" 05:51:01.092
NOTIFY_MODULE_COMPLETION ModuleName="EasyAuthModule_64bit", Notification="AUTHENTICATE_REQUEST", fIsPostNotificationEvent="true", CompletionBytes="0", ErrorCode="The operation completed successfully.
(0x0)" 05:51:01.092
I take it the error is happening when you call client.GetPush().RegisterAsync()? This is currently an issue and we are deploying a fix on the Azure side to fix this. In the interim, you can see the fix for this here: https://adrianhall.github.io/develop-mobile-apps-with-csharp-and-azure/chapter5/android/

Playhaven HTTP error= "403 Forbidden" response= "invalid signature";}

I am a newby who purchased a reskin app and I'm having problems when trying to get the ads to pop up while in Xcode 7 testing on my iphone. I followed the steps to enter the token and secret ID codes after registering the app in playhaven but I keep getting the below error when running the test on Xcode in the debug area.
Stackoverflow is my last resort as the guy who sold me the app can't help...
Playhaven-1.24.0 Request received HTTP response: 403
Playhaven-1.24.0 Request finished
Playhaven-1.24.0 Server response
errorbj - null
error - 403 Forbidden
response - invalid signature
I have tried the new SDK but get more errors/bugs
Please help me
Thanks so much
Andy
Seems like playhavens end doesnt communicate with my account and token codes etc, same with Startapp!

Heroku/MongoLab not working

I ma using heroku and mongolab to host my node app.
So far everything had been working great but now everytime I try to access my mongolab dashboard from heroku I get the following 500 error:
HTTP Status 500 - Cannot call sendRedirect() after the response has been committed
type Exception report
message Cannot call sendRedirect() after the response has been committed
description The server encountered an internal error that prevented it from fulfilling this request.
exception
java.lang.IllegalStateException: Cannot call sendRedirect() after the response has been committed
org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:482)
javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:137)
org.objectlabs.http.RedirectValidatingHttpServletResponseWrapper.sendValidatedRedirect(RedirectValidatingHttpServletResponseWrapper.java:77)
org.objectlabs.http.RedirectValidatingHttpServletResponseWrapper.sendRedirect(RedirectValidatingHttpServletResponseWrapper.java:51)
org.owasp.csrfguard.http.InterceptRedirectResponse.sendRedirect(InterceptRedirectResponse.java:59)
org.olabs.mongolabs.util.ErrorPage.doRedirectTo(ErrorPage.java:53)
org.olabs.mongolabs.util.ErrorPage.redirectTo(ErrorPage.java:32)
org.olabs.mongolabs.user.login.LoginGatekeeper.doFilter(LoginGatekeeper.java:63)
org.owasp.csrfguard.CsrfGuardFilter.doFilter(CsrfGuardFilter.java:79)
org.objectlabs.http.RedirectValidationFilter.doFilter(RedirectValidationFilter.java:20)
org.objectlabs.http.HttpFilter.doFilter(HttpFilter.java:23)
org.objectlabs.http.ClickjackingProtectionFilter.doFilter(ClickjackingProtectionFilter.java:68)
org.objectlabs.http.HttpFilter.doFilter(HttpFilter.java:23)
org.objectlabs.http.AddDefaultCharsetFilter.doFilter(AddDefaultCharsetFilter.java:50)
ch.qos.logback.classic.helpers.MDCInsertingServletFilter.doFilter(MDCInsertingServletFilter.java:51)
note The full stack trace of the root cause is available in the Apache Tomcat/7.0.52 logs.
Apache Tomcat/7.0.52
I am trying to access this url:
https://addons-sso.heroku.com/apps/my-app/addons/mongolab:sandbox
have I dont something wrong??
Apologies for the confusion. For your protection, we have expired all passwords after the heartbleed issue was announced this week and it appears that while you usually SSO in from Heroku you do actually have a password with us.
You appear to have hit an edge case with that code. You should be forced to your user info screen where you can update your password, but it appears you're tripping over an error. Could you write us at support#mongolab.com so that we can identify your account and work through the issue with you?

Resources