We have several action console projects. But recently I could not access to one of our action console projects.
Normally I will access from list in here:
https://www.screencast.com/t/CWlbqhRFc
But now it always show error when I click to one of our projects in there.
https://www.screencast.com/t/b6DmCIcmDsec
I contact with google and ask them for helping. They said that it is caching problems and ask me clear cache on browser. I did it but error still happen. Many other members of this projects also got that error (We shared account of project with some members).
Does someone know the reason of this bug and how could I fix it?
Please check the Roles you have for the project. You need to give Viewer Role to all the members of the project who are getting this error.
Please have a look into this Stackoverflow post as well.
There are a high chance there are a problem in google server. Because after we add a new device model. We could access our project again.
Related
What I am trying to achieve is to archive the app and still have a working consent form on the app.
Although this piece of code is deprecated and says to use ORKInstructionStep I haven't found anywhere how to use ORKInstructionStep instead of ORKVisualConsentStep.
Whenever I try to Archive the app I keep getting this problem. Still, I also can't remove the ORKVisualConsentStep because I haven't been able to find anywhere how to add the consentDocument otherwise.
I've looked at so many other tutorials and all of them use the ORKVisualConsentStep and haven't seen anyone that has had this problem show how to still keep the consent form working. I can get the app running on a phone but I can't get it to archive so not entirely sure what is going on.
Any insight would be beneficial thank you
If you don't know how to added all frameworks, libraries and Embedded contents then you can find shown below what I shared and you can remove it. Please check after your local files remove it.
I managed to fix the problem by using cocoapods to install the ResearchKit framework instead of dragging ResearchKit into my project. It now archives however I had to comment out this line of code instructionStep.imageContentMode = .scaleAspectFit for my survey tasks.
Hi everyone I am experiencing a problem with my Backpack license, I bought the license for a single project, and I have inserted the license into my .Env file as described in the documentation:
BACKPACK_LICENSE=XXXX-YYY-ZZZZ-XXXX-YYY-ZZZZ.
And set APP_ENV=production.
The system seems to recognise the licence correctly (no yellow warning is shown when logging in), however when I try to edit my users, the yellow warning appears with the words: "User editing is disabled in the demo version".
What's wrong?
I should point out that I have not activated the cache, but as a test I have also run the command as suggested: php artisan config:clear, but I still get this warning.
Can anyone help me? Thank you.
It sounds like you've created your project starting from the Backpack demo. That's just an example Laravel + Backpack installation, to show off its features, it should not be used for real-life projects. Notice the demo docs page says:
Don't use this demo to start your real projects. Please use the recommended installation procedure. You don't want all the bogus entities we've created. You don't want all the packages we've used. And you definitely don't want the default admin user. Start from scratch.
I recommend you create a new Laravel project, then install Backpack on top of it, then copy-paste your custom code in that new project. That will not only fix the inability to edit things, but many other problems like the ones listed in the quote above.
I apologize if this has been answered in another post, I can't seem to find it if it has. Anyway, I have built a back end utility for a fellow streamer friend of mine but I can't seem to figure out what I'm doing wrong when it comes to deploying it. This is a project that will be expanded on in the future, and possibly have more windows form projects. So here is what I am running into (With Pictures):
Here is my solution explorer with the projects:
When I go to build the deployment I've tried making all the projects "outputs" and got this error. Thinking it was there were too many Project Outputs I changed it to where the startup project would be the output and the others would be either source or content files. Still got these errors. Here is the File System Setup:
And when I go to run the build to create the deployment, here are the errors I receive:
I don't know/don't see what I am doing wrong here and would very much appreciate a point in the right direction. Thank you all so much in advance.
Check your updates. I remember there is an option to review or check the status of latest updates.
I found this article about that issue but it looks like a general error with updates or the installation
It is not too long but maybe it does not help. I hope it helps, good luck
I am trying to set up a new project and I receive the below error. I hit "retry" but the error shows again. I have tried in different browsers & cleared all cache but issue continues.
"Oops, something went wrong. Project creation operation failed. Please retry project creation."
CTA: Try again
I assume your issue may have something to do with your custom process template. Azure Devops supports default processes like Basic, Agile, Scrum, and CMMI, also it supports customize an inherited process.
Check which process model do you select when you create the project, I think the issue would go away if you select the default process to create the project. And that issue occurs when you try to create one project based on bad process model.
When you create the project, test with different WIT and you can locate the bad one:
Hope it helps and if i misunderstand anything, feel free to correct me.
I'm trying to create a web app integration for Box.com that is available from folders, like the "Send with Gmail" or "Send to Chatter" actions. It seems that integrations that we create from http://developers.box.com only work from files, and not from folders.
I did something similar to that in the past and I vaguely remember that the Box.com support team had to modify by action from their back-end to enable it; I compared integrations in my previous app with the new one I created and I see no visible difference in the configuration.
Has anyone done something similar recently and know the current procedure? I also tried opening a support case from their website and it hasn't been answered either.
The Box support team got back to me on this one and changed the configuration of my web app integration. It's now working the way I expect. They confirmed that they're the only one capables of doing this configuration change - it's not possible to do it from developers.box.com. If anyone needs that - just open a support case on community.box.com and they'll do it for you.