I want to create a robo script for test lab in firebase. When I click on Record Robo Script I get a prompt No suitable run configuration found in Andriod Studio.
enter image description here
Make sure that there is at least one run configuration in your Android Studio project, for example, a run configuration to run/debug your app.
Related
i Found 0 Firebase projects.
✔ Enter a project id for your new Firebase project (e.g. my-cool-project) · onoja
i New Firebase project onoja created succesfully.
FirebaseCommandException: An error occured on the Firebase CLI when attempting to run a command.
COMMAND: firebase projects:create onoja --json
ERROR: Failed to create project. See firebase-debug.log for more info.
This might be caused because you're using a new firebase account on Google or because you haven't set up the proper analytics on your Google firebase account.
I got rid of this by going into Google and setting up the project manually with all their various dialogues and then from thereon all other projects did not have this error in the CLI
if you just start using flutterfire configure for the first time. It means you haven't agreed any terms of use. You should go to firebase console on website first. Then start to build any project you want. You would asked to sign some papers during this process. Once it's done, you could use the terminal without the same error.
try
$ firebase login --reauth
if it does not work try
Open terminal.
vim .zshrc
Press "i" key to activate insert mode.
add export PATH="$PATH":"$HOME/.pub-cache/bin"
Press "Esc" then write :wq in terminal and press enter to exit vim.
Reopen the terminal and check "flutterfire --version"
firebase login
flutterfire configure
if the solution above does not work try to create a project on firebase console manually, and in visual studio command flutterfire configure
I solved the problem of creating a Flutter project in the command line.
Simply, the Project name should be less than 30 characters.
Please I hope you get the correct answer.
^^
Inside the google cloud platform, in the test lab, I uploaded an .apk and we have a new version that we need to test. How do i upload a new version? and how do i delete the old version? I can find no documentation on this matter at all.
Referring to the Test Lab found in firebase under Quality
https://console.firebase.google.com
Steps to run a new tests in the Firebase Console:
Navigate to the Firebase Console
Select your Firebase project in case you have multiple.
In the left-side navigation, click Test Lab under the Quality section.
It will show you your most recent test. There is a button on the top right of the test table named Run test. Click it and select what type of test you want to run.
On the next screen you will have options to upload the app and test APK.
Here's a picture what the button looks like:
Note, you can also do this from the command-line with gcloud.
Please note that there's no need to delete old APKs. Every time you run a test in Test Lab, simply provide the current APK you wish to test.
I followed the instructions, and deployed a simple web yesterday. At first, it kept showing the default website, saying " you've deployed successfully...", not my web.
Also, the 'firebase open' command + "Hosting: Deployed Site" leads to a undefined site:' undefined.firebaseapp.com '.
But, magically, about an hour later when I open the link from 'firebase console' again, the web showed up... I am not sure whether 'firebase open' command worked cause I didn't try.
Today, I added some features, and deployed again. In the firebase CLI, it said deployed. But, the link still showed the old version.
I'll catch up an hours later to see whether it works, but even it works, it takes too long.
has anyone had the same experience? what's wrong with my web?
Thanks.
This is how I solved this issue for my angular 7 app deployment on Firebase hosting:
ng build --prod
go to dist/myproject and run command Firebase init and...
I went to dist/myproject that now contain build files along with Firebase related files. Copy all files except Firebase related files to dist folder in side dist/myproject.
there you will get overwrite warning just select overwrite option.
after copy process completes, run command Firebase deploy.
after completion of process go to shown URL and there you will find your running app.
Our automated build process is as follows:
The build script fetches the latest version of the repository into a clean directory
It runs the build using the following command line command
devenv SolutionFile.sln /rebuild "ServerDeployment|Any CPU" | out-file -FilePath $BuildOutputFile
I want this to run unattendend.
But then the build pauses to display a modal dialog:
An error occurred when applying the IIS Express settings to server URL 'http://localhost:60143/' for project 'CMS.Website'. You may have to manually edit the applicationHost.config file and make the changes for your site to run correctly.
I have to press OK for the build to continue. This is no longer a working unattended build.
I see that Visual Studio has automatically generated a file .vs\applicationhost.config in my build folder.
I compared this file with the file .vs\applicationhost.config in my development folder. I can see the version of the file in my development folder (which doesn't cause errors) has an extra site entry under the node: //configuration/system.applicationHost/sites
How can I make this message box go away? Obviously I don't care if this runs on IIS Express or not, because I'm performing a build to be deployed on a different server.
Possible solutions (that I don't particularly like) are:
Check the file .vs\applicationhost.config into the repository, so it gets checked out as part of the build rather than regenerated
Modify my build script so it copies the template file from C:\Program Files\IIS Express\config\templates\PersonalWebServer\applicationhost.config and then modifies this XML file to manually add the new site entry
Is there a better solution to my problem?
In my case, the debug settings were stored as part of the Web Application's .csproj file (which is part of the checked-in repository).
It should be stored as part of the .csproj.user file (which does not get checked in).
In my project settings I needed to make sure that 'Apply server settings to all users (store in project file)' was unchecked.
Once I unchecked this setting the automated build ran from start to finish without presenting a modal message box.
I have converted a Win32 Application to UWP using MakeAppX and it doesn't seem to run. When I click the icon in the start menu literally nothing happens except a busy icon briefly appears on the cursor.
I completed the same process with Notepad++ and all it's DLLs and that worked fine (using the exact same manifest file, just changing the exe)
My questions are:
Where does the UWP save files that it creates/temporary files etc? If I run an executable and it generates files next to it, where would that be when you run a UWP?
Can I set that location in the AppxManifest?
Is there anyway to see if it has run correctly or not?
Edit:
Could this be a file permissions issue? My application needs to write to 'C:\MyFolder' & creates a folder with a load of files next to the executable upon startup and that doesn't happen.
So looking into this a bit more I came across this blog which discusses preparing for conversion. I think the above file accesses probably contravene the following:
Your app writes to the install directory for your app. For example, your app writes to a log file that you put in the same directory as your exe. This isn't supported, so you'll need to find another location, like the local app data store.
This looks like a fairly halting issue, am I correct in that assumption?
If your app is writing to the install directory you will need to change that code to write to your local app data folder instead, as the preparation guide calls out.
Write operations to the install directory are not allowed in order to ensure the ability for the app deployment stack to perform seamless, differential updates and clean uninstalls of your app.
Btw, to debug through your app launch failures you can do the following in Visual Studio: Debug -> Other Debug Target -> Debug Installed App Package -> select your app from the list of installed apps.