I'm learning flutter and trying to create a chat app with Flutter and Firebase.
When I'm testing it, I got a message from another app. When I replied to it, my terminal also catch the message with content, timestamp, and created_by information.
Is this a bug? Should I contact the application dev team? Am I in trouble for hacking??
I am confused right now, please help!!
That's happening because the other app might be using print statements, and as you are currently debugging apps and is in development mode, it prints the content in your console.
That's why it is always recommended to use log instead of print during development.
Related
I have a multi-page web application written in Flutter which uploaded on Firebase hosting . All the pages work fine but half of the homepage is grey. Photo attached. Really appreciate for help.
Also, I'm getting this error when I run: flutter run -d chrome --release
Oops; flutter has exited unexpectedly: "ProcessException: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event
log or use the command-line sxstrace.exe tool for more detail.
Command: C:\Users\abc\AppData\Local\Google\Chrome\Application\chrome.exe --user-data-dir=C:\Users\abc\AppData\Local\Temp\flutter_tools.2b59d482\flutter_tools_chrome_device.4fad7966 --remote-debugging-port=2576 --disable-background-timer-throttling --disable-extensions --disable-popup-blocking --bwsi --no-first-run --no-default-browser-check
--disable-default-apps --disable-translate http://localhost:11541".
I have also faced same issue while host web app in firebase.
the issue is not in firebase host. the issue is in your code. your code will completely work in debug mode. but not in released mode.
check every warning in logs.
it is mostly happen because of wrong use of expanded or flexible widget
I'm reporting a very strange problem.
I have an app developed in Flutter and I have correctly integrated the Firebase library for using the Dynamic Links service.
The problem is when short links are open on a mobile device, it shows a screen with the message "Save my place in the app. A link will be copied to continue to this page", and a button OPEN to continue.
Using your link debugging tool everything seems ok
When I develop directly in debugging mode the problem does not present itself.
When I install the app from TestFlight sometimes it works and sometimes it doesn't. It seems random.
the problem could be that the app is not yet available on the store ?
I'm trying to add the Crashlytics SDK to my Android app, but it seems to be having trouble communicating with the Firebase servers. I've followed all of the instructions per the docs, but the Crashlytics tab in my console has been stuck on this screen for about 6 or so hours:
crashlytics add sdk screen.
I would (ideally) get this to just work™️, but if not then I'd like to be able to restart the process, but I also don't know how to do that.
Thanks in advance!!
I figured it out - I was mistakenly using the same appplicationID as another one of my projects, so Firebase was getting confused - making an entirely new project with a different applicationID fixed my problem.
if you followed all the steps as latest documentation..crash the app( use fatalError() for crash) using button action, this trick works for me.
https://firebase.google.com/docs/crashlytics/get-started?platform=ios&authuser=0#force-test-crash
For me Create a crash on button in project Relaunch application by simulator not by Xcode and It worked for me.
I'm having some trouble integrating my app with the parse4cn1 lib. I followed the tutorial published on this link and the app registers normally on the Parse Server as an installation but when I try to send a push to Android devices they simply aren't being sent.
I haven't tried on iOS yet, since I figured I'd start with Android, and I'm working with a new GUI Builder app if maybe that affects something for any reason.
Thanks for your help.
Ok, I have found the problem, it was related to parse not the parse4cn1 lib. I'm actually new with parse and backend in general, I wasn't aware I had to run the pm2 restart command after modifying the cloud code.
It's working now, thanks!
I'm writing this post because I don't know what I can do.
I'm developing an big app for iOS with a lot of users for my company; to log error and crashes I'm using Microsoft MobileCenter (Analytics and Crashed ver. 0.6), Xamarin.Forms ver. 2.3.3.168 and a lot of components such as Xam.Plugins, SQLite, PCLStorage, SharpZipLib.
As MobileCenter request the minimum target version for the app is 8.
Apart from minor bugs, the big problem is difficult to explain. I'm trying to ask you an advice.
The app is working fine. If I test it, I can't have any problems. At same point the app crashed for any apparently reason. No logs, no crashed, no nothing in MobileCenter. From this moment it's impossible to start the app and I can't have any logs about it: I can see the splash screen but after than the app is crashed again. It seems the problem raises after taking photo with camera.
When the app starts, it deletes images (if there are any in the folder), send a file to my server, and check with CrossDeviceInfo what the OS version is. Then the first page is called.
I tried to understand the problem to read the log in Xcode after connecting my device to my iMac but it's incomprehensible.
If I try to read the View Device Logs I can find one crash for my app but the log is still incomprehensible for me.
Then from Xcode I tried to open Organizer and under Crashes...
If I connect the device with this issue to my iMac and I deploy the app on it, the app is working fine. How can I understand where the problem is to fix it?
Update
In my App.xaml.cs I initialise MobileCenter like the following code:
public partial class App : Application
{
public App() {
// my code
}
protected override void OnStart()
{
MobileCenter.LogLevel = LogLevel.Verbose;
MobileCenter.Start(typeof(Analytics), typeof(Crashes));
}
}
It's Benjamin. I've already replied to you issues in our intercom but I wanted to reply to your issue here.
This scenario is not an actual crash but a kill of the app process by the operation system. The SDK runs as part of the app process and therefor can’t ever figure out that this kill even happened because the process is fully removed right away. Technically this is not a crash from an SDK perspective that it can detect and provide details for. Every single 3rd party SDK has this limitation and there is no way around it as Apple doesn’t provide the technical possibilities to do so.
In addition, none of your provided crash reports contain any reference to Mobile Center thus I can rule out our SDK is the cause of the kill.
I hope you find the cause for the issue.🖖