When I try to connect Video call, It's connecting but after few seconds activity get destroyed.
I am trying to connect my video call but after sometime it get disconnected automatically
and in my Logcat I get error
2023-01-09 18:47:23.763 11645-12011/E/agora.io: [LVT]: Faile to remove video filter when track is enabled.
2023-01-09 18:47:23.771 11645-12011/E/agora.io: [LATMP]: invalid local_playback_source_.
2023-01-09 18:47:23.771 11645-12011/ E/agora.io: [LATMP]: local playback has been disabled.
2023-01-09 18:47:23.773 11645-12011/ E/agora.io: [LATMP]: invalid local_playback_source_.
2023-01-09 18:47:23.773 11645-12011/ E/agora.io: [LATMP]: local playback has been disabled.
2023-01-09 18:47:23.775 11645-12011/ E/agora.io: [LATMP]: local playback has been disabled.
2023-01-09 18:47:23.775 11645-12011/ E/agora.io: [LATMP]: local playback has been disabled.
2023-01-09 18:47:23.775 11645-12011/ E/agora.io: [LATMP]: local playback has been disabled.
2023-01-09 18:47:23.783 11645-12011/ E/agora.io: [LATP]: local playback has been disabled.
2023-01-09 18:47:23.784 11645-12011/ E/agora.io: [LATP]: local playback has been disabled.
2023-01-09 18:47:23.786 11645-12011/ E/agora.io: [LATP]: local playback has been disabled.
2023-01-09 18:47:23.794 11645-12011/ E/agora.io: [AFC]: failed to find the to be removed audio filter remote_mixed_playback.
2023-01-09 18:47:23.802 11645-12026/ E/agora.io: [CommonUtility] [closeGravityMonitor] mOrientationListener is null!
Related
Simplest Alamofire sample. main.swift:
import Alamofire
import Foundation
AF.request("https://httpbin.org/get").response { response in
// debugPrint(response)
}
RunLoop.current.run()
Writes to debug console output e.g:
2021-10-02 14:45:28.198648+0300 AlamofireExp1[4891:191952] [logging] volume does not support data protection, stripping SQLITE_OPEN_FILEPROTECTION_* flags
2021-10-02 14:45:28.199070+0300 AlamofireExp1[4891:191952] [logging] volume does not support data protection, stripping SQLITE_OPEN_FILEPROTECTION_* flags
2021-10-02 14:45:28.626982+0300 AlamofireExp1[4891:191952] [connection] nw_endpoint_handler_set_adaptive_read_handler [C1.1 54.159.86.231:443 ready socket-flow (satisfied (Path is satisfied), viable, interface: en0, ipv4, dns)] unregister notification for read_timeout failed
2021-10-02 14:45:28.627089+0300 AlamofireExp1[4891:191952] [connection] nw_endpoint_handler_set_adaptive_write_handler [C1.1 54.159.86.231:443 ready socket-flow (satisfied (Path is satisfied), viable, interface: en0, ipv4, dns)] unregister notification for write_timeout failed
2021-10-02 14:45:28.756444+0300 AlamofireExp1[4891:191941] [logging] volume does not support data protection, stripping SQLITE_OPEN_FILEPROTECTION_* flags
2021-10-02 14:45:28.756749+0300 AlamofireExp1[4891:191941] [logging] volume does not support data protection, stripping SQLITE_OPEN_FILEPROTECTION_* flags
Question: How to suppress this garbage (for me) output to debug console?
This isn't Alamofire logging, this is logging from the underlying OS. Unfortunately there's no good way to disable it. Technically you can add the OS_ACTIVITY_MODE environment variable set to disable for your builds, but that disable all OS module functionality, including your own OSLogs and signposts, among other features, so it's not recommended.
I am using EclipseLink with JTA. when I run the application using WebLogic server version(12.2.1.3.0) faced the following issue
[EL Warning]: 2020-06-03 16:17:13.679--ClientSession(1584629836)--Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLRecoverableException: The connection has been administratively diabled. Try again later. The action was taken by a console or administrative command. java.lang.Exception: It was disabled at Wed Jun 03 16:17:13 IST 2020
at weblogic.jdbc.common.internal.ConnectionEnv.disable(ConnectionEnv.java:454)
at weblogic.jdbc.wrapper.JDBCWrapperImpl.removeConnFromPoolIfFatalError(JDBCWrapperImpl.java:159)
<Forcibly releasing an already closed connection "[weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection-platform-2420, ]" back into the data source connection pool "platform".>
PS - Not facing this issue with WebLogic version(12.2.1.2.0)
As per a somewhat dated oracle article, there are a number of causes, such as the database going down (temporarily or longer), or bugs in WLS itself. The bugs mentioned have been fixed, but that doesn't mean something new wasn't introduced or just some setting you had in 12.2.1.2.0 doesn't work or apply the same in 12.2.1.3.0.
Solutions vary, but check that the datasource is disabled and manually enable it through the console, and change the datasource settings so that isn't disabled unnecessarily in the future:
https://docs.oracle.com/cd/E23943_01/web.1111/e13737/ds_tuning.htm#JDBCA180
Internet Explorer Driver hangs for an hour during CreateSession Call. It hangs for an hour to find window handle for Internet Explorer Server and this issues happens intermittently. Has anyone experienced a similar issue ?
InternetExplorerDriver Version: 64-bit, 3.141.59
Microsoft Windows Server 2019: 64 bit
BrowserFactory::LaunchBrowserUsingIELaunchURL
D 2020-05-15 03:36:53:582 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(250) Starting IE using the IELaunchURL API
D 2020-05-15 03:36:54:386 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(204) IE launched successfully with process ID 4888
D 2020-05-15 03:36:54:386 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(210) Process with ID 4888 is executing iexplore.exe
T 2020-05-15 03:36:54:386 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(368) Entering BrowserFactory::AttachToBrowser
D 2020-05-15 03:36:54:386 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(378) Using Active Accessibility to find IWebBrowser2 interface
T 2020-05-15 03:36:54:386 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(427) Entering BrowserFactory::AttachToBrowserUsingActiveAccessibility
D 2020-05-15 04:36:59:140 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(447) Found window handle 0000000000040298 for window with class 'Internet Explorer_Server' belonging to process with id 4888
T 2020-05-15 04:36:59:140 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(332) Entering BrowserFactory::GetDocumentFromWindowHandle
D 2020-05-15 04:36:59:611 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(399) Ignoring zoom setting: 0
T 2020-05-15 04:36:59:611 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(591) Entering BrowserFactory::GetBrowserZoomLevel
T 2020-05-15 04:36:59:636 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(631) Entering BrowserFactory::GetZoomLevel
D 2020-05-15 04:36:59:671 C:\Projects\webdriver\cpp\iedriver\BrowserFactory.cpp(711) Browser zoom level is 100%
I 2020-05-15 04:36:59:672 C:\Projects\webdriver\cpp\iedriver\IECommandExecutor.cpp(1366) Persistent hovering set to: 1
T 2020-05-15 04:36:59:672 C:\Projects\webdriver\cpp\iedriver\ProxyManager.cpp(103) ProxyManager::SetProxySettings
D 2020-05-15 04:36:59:672 C:\Projects\webdriver\cpp\iedriver\ProxyManager.cpp(119) Using existing system proxy settings.
T 2020-05-15 04:36:59:672 C:\Projects\webdriver\cpp\iedriver\DocumentHost.cpp(36) Entering DocumentHost::DocumentHost
T 2020-05-15 04:36:59:672 C:\Projects\webdriver\cpp\iedriver\CookieManager.cpp(48) Entering CookieManager::Initialize
T 2020-05-15 04:36:59:672 C:\Projects\webdriver\cpp\iedriver\Browser.cpp(38) Entering Browser::Browser
T 2020-05-15 04:36:59:672 C:\Projects\webdriver\cpp\iedriver\Browser.cpp(383) Entering Browser::AttachEvents
I am following this tutorial https://www.youtube.com/watch?v=S43-A1N_COE.
When I start recording, error “Recording unavailable” was appeared.
Already browse the same error, but not getting fixed yet.
Here my jicofo.log and jibri.log
https://codeshare.io/5NRdbV
I think the main point why I getting this error because of this logs
INFO: [29] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Failed to start a Jibri session, no Jibris available
And don’t know how to solve it.
Are that some settings that I missed?
Update
When I try to install Jibri on another server, its worked. I follow this (docs)[https://docs.easyjitsi.com/docs/gettingstartedjibri] btw.
Errors:
02/15 09:33:30: Launching app
$ adb push C:\Users\hp\AndroidStudioProjects\recevienotfirebase\app\build\outputs\apk\app-debug.apk /data/local/tmp/com.example.hp.recevienotfirebase
$ adb shell pm install -r "/data/local/tmp/com.example.hp.recevienotfirebase"
Success
$ adb shell am start -n "com.example.hp.recevienotfirebase/com.example.hp.recevienotfirebase.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Client not ready yet..Connected to process 2360 on device Nexus_6P_API_24 [emulator-5554]
I/art: Not late-enabling -Xcheck:jni (already on)
W/art: Unexpected CPU variant for X86 using defaults: x86
W/System: ClassLoader referenced unknown path: /data/app/com.example.hp.recevienotfirebase-1/lib/x86
I/InstantRun: Instant Run Runtime started. Android package is com.example.hp.recevienotfirebase, real application class is null.
[ 02-15 09:33:38.693 1497: 1520 D/ ]
HostConnection::get() New Host Connection established 0x8fdb9800, tid 1520
W/System: ClassLoader referenced unknown path: /data/app/com.example.hp.recevienotfirebase-1/lib/x86
D/FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
W/InstanceID/Rpc: Found 10012
D/FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
I/FA: App measurement is starting up, version: 10084
I/FA: To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
D/FA: Debug-level message logging enabled
D/FA: AppMeasurement singleton hash: 91568628
V/FA: Collection enabled
V/FA: App package, google app id: com.example.hp.recevienotfirebase, 1:1056127560632:android:663d67b615c99e63
I/FA: To enable faster debug mode event logging run:
adb shell setprop debug.firebase.analytics.app com.example.hp.recevienotfirebase
V/FA: Registered activity lifecycle callback
I/FirebaseInitProvider: FirebaseApp initialization successful
V/FA: State of service unknown
V/FA: Checking service availability
W/GooglePlayServicesUtil: Google Play services out of date. Requires 10084000 but found 9452470
D/FA: Service container out of date
V/FA: Setting useService: true
V/FA: Using measurement service
V/FA: Connecting to remote service
W/GooglePlayServicesUtil: Google Play services out of date. Requires 10084000 but found 9452470
W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter android.support.graphics.drawable.VectorDrawableCompat.updateTintFilter(android.graphics.PorterDuffColorFilter, android.content.res.ColorStateList, android.graphics.PorterDuff$Mode) would have incorrectly overridden the package-private method in android.graphics.drawable.Drawable
V/FA: onActivityCreated
V/FA: Using measurement service
V/FA: Connection attempt already in progress
V/FA: Activity resumed, time: 51631
W/gralloc_ranchu: Gralloc pipe failed
[ 02-15 09:33:52.817 2360: 2360 D/ ]
HostConnection::get() New Host Connection established 0x9e59ea40, tid 2360
W/FA: Service connection failed: ConnectionResult{statusCode=SERVICE_VERSION_UPDATE_REQUIRED, resolution=null, message=null}
I/OpenGLRenderer: Initialized EGL, version 1.4
D/OpenGLRenderer: Swap behavior 1
V/FA: Session started, time: 61634
I/FA: Tag Manager is not found and thus will not be used
D/FA: Logging event (FE): _s, Bundle[{_o=auto, _sc=MainActivity, _si=-2727167516359703917}]
V/FA: Using measurement service
V/FA: Connecting to remote service
W/GooglePlayServicesUtil: Google Play services out of date. Requires 10084000 but found 9452470
W/FA: Service connection failed: ConnectionResult{statusCode=SERVICE_VERSION_UPDATE_REQUIRED, resolution=null, message=null}
W/FA: Tasks have been queued for a long time
Google Play services out of date. Requires 10084000 but found 9452470
You may want to check this thread which states that you'll get this error when the activity is not exported. Be noted that the activity has to be exported to be accessible from adb.
Also, based from this SO post, you have to add the following to your android manifest: <action android:name="com.google.firebase.INSTANCE_ID_EVENT"/> or maybe the problem was that the onTokenRefresh() method was not called when the app was starting. Try calling FirebaseInstanceId.getInstance().getToken() in the MainActivity and see if it works.