I am using Firebase remote config where I have created parameters and assigned them values using conditions. After the latest Firebase update, I am unable to successfully remove any conditions assigned to parameters. When I remove the condition and save the changes and click on Publish Changes, the page is loaded and shows a popup message "published" but the condition is still present inside the parameter.
I have the same. Only removal condition from conditions section helps.
Related
I have created a new mimik developer account, and I was trying get the edge access token using the command "mimik-edge-cli account get-edge-access-token -t <--id token-->". But I am getting an "Error" as response.
I have tried with my previous account and in that case i am able to get the access token as shown below. Same issue happened for raspberrypi too.
why it is not able to get the access token while using a new account?
Please make sure to copy the ID Token from developer portal correctly, In most cases there might be a hidden character copied. Maybe just try copying the text by highlighting with mouse from first character to the last. Do NOT use the copy to clipboard button. Also please make sure that the edgeEngine on the PI is not associated already by checking with:
mimik-edge-cli account get-me
When you input command above, if you see an ID for value "accountId:" then your PI is already associated an CANNOT be associated again. You have to un-associate first and then associate with the new ID token from new account/project. You can verify that un-association is successful when above command shows empty value for "accountId:"
FOR FUTURE REFERENCE:
Please only tag questions with edgeSDK if it is related to FreeRTOS platform. For all other platforms, please use tag edgeEngine
I am trying to track a GitLab issue no matter in what project it may reside.
An issue is normally created in GitLab within the context of a project. If it is moved to another project, the issue is closed and a new issue is created. The original issue tracks the new location using the moved_to_id. The problem is I have no idea how to follow this moved_to_id value using the GitLab API v4. GitLab does not honour the typical REST-like behaviour where you can retrieve an entity by its ID.
For example, if I call https://gitlab.com/api/v4/issues/ I'll get a list of issues as objects: these objects have a set of fields: title, description, state, ..., id and iid. The iid is the user-friendly id of an issue within a project. But what is the id and how is it useful? I can't retrieve an issue using this id - at least not using expected ways...
Consider an issue exists in https://gitlab.com/api/v4/issues/ with id == 29564819,
https://gitlab.com/api/v4/issues/29564819 returns a 404.
https://gitlab.com/api/v4/issues/29564819/ returns a 404.
https://gitlab.com/api/v4/issues/29564819?scope=all returns a 404
https://gitlab.com/api/v4/issues/?id=29564819 returns all the issues (no effect using parameter).
Can I retrieve an issue without a project? Do I have to resort to using labels?
If a user is not a member of a private project, a GET request on that project results in a 404 status code.
Only administrators can retrieve issue by its id.
The preferred way to do this is by using personal access tokens.
GET /issues/:id
I'm using Firebase for my iOS app. For users on old versions of my app I want to be able to force them to update their app from App Store to be able to continue using the app. For this I'm checking a remote config value in the app if it's true the user will get a full screen message to update. In Firebase Console Remote Config I'm checking the version of the app to set the remote config value to true/false. See image below.
The problem is that I want to be able to use "where version < X" to set the value or if that is not possible at least be able to pick more than one version (where version is X or Y or Z).
This must be a common use case but I can't figure out how to do this. Anyone know how to? Can I use regex, but how?
Add a remote config value that declares the minimum required version like this
Then you implement the "is old" logic on client side by checking the client's version number against the provided remote config value. If the check fails, then you display the "update your app" screen.
Make sure to set the default/fallback value on the client to a version number that is not forcing them to update (version 0.0.0 for example).
You can configure remote config conditions for different platforms and version number values if you don't have a synchronized version numbering across your platforms.
I use ELK and I've just sent DELETE /* request to http://localhost:9002. Then I refreshed Kibana page but I got this error
Index Patterns
Warning No default index pattern. You must select or create one to continue.
In order to use Kibana you must configure at least one index pattern. Index patterns are used to identify the Elasticsearch index to run search and analytics against. They are also used to configure fields.
How to fix it?
Sorry, might be stating the obvious here, but are you shipping any data? This message is usually displayed when there the pipeline is not functioning correctly - i.e. logs not being forwarded from Logstash to Elasticsearch.
I am building a very simple cron job backup system for a friend's firebase app;
I have PHP code, using firebase-php that can communicate with the firebase and the API docs state that adding the'?format=export" parameter will retrieve a .json file. Cool, so far.
My question is this: What path (after the firebase URL) is required?
The API doc appears to state that it should be /.json but it returns a 404 /json/ works on the simulator, but also returns a 404 in testing
(note: looking for a single text file, similar to the "Export json" data dashboard, if possible)
Thanks in advance.
The path defined the portion of the Firebase data tree that is being loaded. That means that you can load /any/possible/string and it will return a value, though that value is likely to be null unless you've written data to that path. Also note that without a defined extension (i.e. .json) you'll be attempting to load Firebase's in-browser graphical debugger.
In short, if you're using the REST API, you'll always want to end your paths in .json, but nothing else is required, i.e. https://<your-firebase>.firebaseio.com/.json is perfectly valid, and would download your entire Firebase. The format=export parameter ensures that any Firebase priority values are preserved in your JSON output, under the key .priority at any node, where they would normally be excluded.