I followed all instructions on this link https://fabric.io/kits/android/crashlytics/install but I still cannot see my app in the dashboard. This was never an issue for me before.
Clicking on the +New App only brings me to selecting which kits to use.
Then when trying to distribute it says project is inactive..
The project is definitely not inactive..
How do I fix this?
Related
I'm getting this error when opening VS Code. Does anyone know what it means? I've done some research but didn't get any relevant information :(
I've tried creating a workflow to see if the error disappeared, but it didn't.
It seems that react native is asking for a workspace to start but is it asking that in the first place? Can I disable react native from running when opening VS Code?
The folder opened when the screenshot above was taken was the folder it opens by default, I believe it's the mac "home" personal folder, and I have a folder called "git" inside of it, with all projects.
Given the date of this posting (2023-02-07), you're probably on version 1.10.0 of the extension. This sounds like this bug report in the microsoft/vscode-react-native GitHub repo: [Bug] Extension activating when it shouldn't #1891.
A fix is coming in version 1.10.1.
But it is taking some time and has not been release yet at the time of this writing 2023-01-31:
we're facing some problems in the last release process, recently we're waiting for new publishing PAT access to republish 1.10.1 again, maybe it will publish on marketplace on next week. We have nightly version for extension in marketplace as well, maybe you can use it now.
For now, you can try installing the nightly version.
Also, note from the extension's readme documentation:
Before going any further make sure that you:
have a working React Native environment.
have the emulator utility available in your PATH if you're developing Android applications.
[...]
Got it, this annoying log came from React Native Tools extension. They specify the requirements in the docs:
In my case, I don't have a specific React Native environment or the emulator PATH is not right.
I'm completely new to React Native, Expo and App development in general.
I'm building a React Native app solely for iOS using Expo. I've finally managed to finish a version I'm happy with, tested with users etc. I've now been spending time adding all the required screenshots, text, info etc to App Store Connect in order to submit the app. While doing that, I learned that iPad app screenshots was mandatory, which I found weird.
I later found that I had "supportsTablet: true" in my App.json file, so it makes sense that it's expecting iPad pictures. After changing this and making a new build and submitting that, it's still a requirement.
After Google a bit I can see that it has been impossible to change this:
Removing iPad support from app
iOS App Submission : remove iPad support
iOS App Submission want to remove iPad support
This led me down the road of trying to upload the app as a new submission. I can't get this to work though. According to this documentation:
https://developer.apple.com/library/archive/qa/qa1623/_index.html
I should change bundle identifier and upload again. Changing this in app.json under expo.ios.bundleIdentifier doesn't work though, as I just get an error that I've already uploaded this app previously.
What are the steps I should do to reupload the app as a new submission, so that I can not support iPad?
In order to upload a new version, you must increase the version and the build number. You can find this if you open the project in Xcode under the General tab and the Identity section. In the same tab, you will see the Deployment Info section where you can untick the iPad. Check the picture attached.
For some reason we needed to change the package-id of our existing android application. We already use Fabric for Crashlytics.
I'm trying to bring that new app up in the Fabric dashboard, but it's not showing there, despite the device log showing no issues (as fas as I can see): device log
Any ideas why the new package-id isn't visible in our dashboard?
Best,
Sven
I experienced a very similar issue to this when building an app with multiple flavours. The solution is to manually specify the package name, and not let Fabric try to automatically grab it, as it tries very hard to "stick" your old package name.
There is a full post available (disclaimer: my site), but essentially you need to use:
Fabric.with(
Fabric.Builder(this)
.kits(Crashlytics())
.appIdentifier(BuildConfig.APPLICATION_ID)
.build()
)
Make sure to include all dependencies on their dedicated gradle.build and meta in manifest file. Next is to throw a force runtime error on your device with internet connection also do not forget to initialize it first with Fabric.with(this,new Crashlytics()). If this doesn't work try to download and install Fabric for Android plugin in Android Studio, restart the IDE and you will see a fabric icon above. Start it and select your package name.
I had the exact same problem, in the log I clearly see that the Crashlytics is in use.
I/CrashlyticsCore: Crashlytics report upload complete: <ID>
But I cannot see my project on the dashboard, and always redirect to the tutorial.
After a Build-Clean and an Android studio restart, build and run the app again to my phone, and voilá, it finds itself. Now working, without any change.
I have the same problem. After hours of researches I resolve this for my application.
First: After adding new flavour, I make changes in Firebase console (added new app in existing project, with production SHA1, changed google-services.json).
After that app does not show in fabric dashboard and fabric plugin in Android Studio. Problem was resolved after linking new app in crashlitycs in firebase console. And after that check your roles, must have Owner role (on Firebase Console Project).
I'm working with several fellow classmates on a simple mobile app in Titanium. I'm running into a problem though, as when I pull the files from github as a new project it isn't classified as a mobile project, just as a blank project. Basically, this keeps me from being able to run the project for any reason, the option to do so is just grayed out. The code works in a new project I create as a mobile app, but for some reason Titanium doesn't recognize the pulled project as something that can be run. I've confirmed that the deployment targets in the pulled project are checked for Android and Mobile Web, is there something else I should be looking for, or a command I need to enter?
Okay, figured it out. I had to go into properties and under project natures I had to put a check next to 'Mobile'. Kind of painful how simple that was, but maybe my question/answer will help anyone else caught by this
I'm developing iOS apps and I'd like to share my apps with TestFlight testers. This is not the problem and works fine (via email). However, when I'm uploading a new build, I'd like to have in-app updates.
The SDK describes this as being possible, but I don't see anything from an update in my app.
I closed the app from "Multitasking".
I added the SDK to my project and in the AppDelegate my TeamToken, Checkpoints, etc. work fine.
Any ideas?
On testflight, have you enabled the force upgrade? (Your Application -> Build -> Build information -> Forced upgrades)
Also please make sure that the activity report is showing your session when you start your app.