Why Crashlytics is not logging? - swift

I am using Crashlytics to log errors and when I try to test it like this:
componentDidMount() {
crashlytics().log('test');
}
however, no logs are sent! Nonetheless, when I use Crashlytics.crash() it works, it logs the error which I can see in the firebase console Crashlytics dashboard.

These logs are sent as part of the crash report and not individually.
In the dashboard when you open a crash, you will see them in the "Logs" tab. Check this: https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=ios#add-logs

Related

Accessing log file in Codemagic

I'm filling in the Codemagic yaml file to perform an iOS deploy for React Native. However, an error occurs while the builder is fetching the signing files:
Executing AppStoreConnect action fetch-signing-files failed unexpectedly.
Detailed logs are available at
"/var/folders/m7/aegaegawegaw323523t232/T/codemagic-09-01-22.log".
To see more details about the error, add `--verbose` command line option.
The error message is too vague. It simply tells me to use --verbose, which returns
[12:28:30] DEBUG > Load JWT for App Store Connect key 'NAME_OF_KEY' from disk cache
[12:28:30] DEBUG > Failed to load App Store Connect JWT from disk cache:
Token is not cached
[12:28:30] DEBUG > Generate new App Store Connect JWT for key 'NAME_OF_KEY'
[12:28:30] WARNING > Executing AppStoreConnect action fetch-signing-files failed unexpectedly.
Detailed logs are available at "/var/folders/m7/aegaegawegaw323523t232/T/codemagic-09-01-22.log".
To see more details about the error, add `--verbose` command line option.
Which still is not enough for me to understand what's going on. My question is how do I access the Codemagic log at the mentioned codemagic-09-01-22.log file?
with Codemagic you can access builder machine via SSH or VNC (https://docs.codemagic.io/troubleshooting/accessing-builder-machine-via-ssh/) to check all logs.
However from the log you provided are you sure you configured correct key name?

Azure communications Web Calling issue

When i use the CallClient of #azure/communication-calling SDK to create a CallAgent, i'm getting 'No CommunicationTokenCredential provided' error even though i'm passing a valid CommunicationTokenCredential
Ex: this.callAgent = await this.callClient.createCallAgent(tokenCredential);
I'm able to successfully deploy a standalone react app & run the following sample application and make a web call as suggested in Microsoft docs. https://github.com/Azure-Samples/communication-services-web-calling-tutorial
But, when I integrate this into my existing React App, I start having issues in creating a CallAgent with the following error:
'azure:ACS:error 27/10/2021, 18:13:48:96 CallClient1:CallAgent1 op:Initialize failed, message=No CommunicationTokenCredential provided,'
I am passing the CommunicationTokenCredential properly while calling the createCallAgent(token) (verified by printing the token as well).
But still, I get this error. Has anyone else faced this issue?

Analytics Kit - When Response Content From Connection inputStream operation exception! 40

I'm trying to implement Huawei Analytics Kit in the app, but unfortunately I faced with a problem, when in debug mode my custom event's are not displaying on the web in App debugging. In logs I can see the following error, that is saying that I have no network or no Internet permission which is NOT true in my case.
W/HiAnalyticsSDK: HttpClient=> When Response Content From Connection inputStream operation exception! 401
W/HiAnalyticsSDK: StreamUtil=> closeQuietly(): Exception when connHttp.getInputStream()!,There may be no network, or no INTERNET permission
I/HiAnalyticsSDK: ReportInstance=> response code : 401
I/HiAnalyticsSDK: SendTask=> events PostRequest sendevent TYPE : oper, TAG : _openness_config_tag, resultCode: 401 ,reqID:530a86a50e7643cb83ec1328b5332fbf
I/HiAnalyticsSDK: SendTask=> is debug mode
Could you suggest me please the source of this kind of problem, because I've already made a full research of documentation and didn't find the solution of this problem. Thanks.
Would you mind provide some further info for further check?
-The version number for Huawei Analytics SDK
-Data storage area selected when analysis service is enabled
-A complete Huawei Analytics SDK log, from initialization to error occured
Error code 401 means unauthorized access or invalid login credential. Please make sure that you have include your agconnect-services.json in your app directory, enable and configure Analytics API correctly in your developer console.
You can refer to this FAQ - https://developer.huawei.com/consumer/en/doc/development/HMSCore-Guides-V5/environment-faq-0000001050162062-V5.
Please go over this doc and make sure that you don’t miss any step - https://developer.huawei.com/consumer/en/doc/development/HMSCore-Guides-V5/android-dev-process-0000001050163813-V5.

Azure mobile services

I've been trying to see the log in console window in azure portal(output) . But i'm not able to see the console output..
Example
I've table tblEmp.
This is my code in tblEmp.read.js
function read(id, user, request) {
console.log("____reading_____");
request.execute();
}
When i execute this , i get the response . But the problem is i dont see console message. Also i've turn on the application logging from Diagnostics logs .
Thanks

An internal error has occurred. The application may still be initializing or the URL used is invalid

When I try opening the dashDB console from Bluemix, I occasionally get the following error message:
An internal error has occurred. The application may still be
initializing or the URL used is invalid. Check the URL and try again.
For more information, view the server log files.
How can I fix this?
The problem seems to be a cookie caching issue.
Get the domain name from the browser window that is displaying the error message. E.g. awh-yp-small02.services.dal.bluemix.net
Open cookie page, for example in firefox:
Search for cookies with the YOUR domain name from step 1.
Select all those cookies and delete them by clicking the 'Remove Selected' button.
You should be able to launch now.
WARNING: the above worked for me, but use the above advice at your own risk.