I started using Parse-on-Buddy on the Buddy.com website recently. In the last couple of days, I am having issues trying to upload any kind of file to any of my classes using the web-browser. If I post a new object from the app I have built for it, the file uploads, but won't from the web. I have tried Safari and Chrome on my MacBook, both with the same results. I've reached out to support but without anyone getting in touch with me, and never answering their phone. Anyone else come across this issue and know a fix?
There is a known issue with dashboard file uploads and app keys, where if any app keys have been created, additionally there needs to be a JavaScript app key created for uploads to succeed. Create one by logging in to the Parse on Buddy dashboard at https://parse.buddy.com, navigating to your app, then going to 'App Settings' -> 'Security & Keys'. Click on the 'Create' button next to the 'JavaScript key' section. Thanks.
Related
I am facing an issue with our web tool that I am unable to solve. I already tried to google a solution but failed to find one.
We have a website where we use JavaScript to record audio from the users microphone via getUserMedia. The first time the user enters a html page on the https website, there is a notification popping up about permission rights. Thats fine, but on Firefox Mobile it doesn't matter if you gave your permission already, you will be asked on every single page again. Thats not the case for every other browser we tried.
So, is this some kind of our error or is it a limitation of Firefox Mobile?
Hope anyone solved that issue already in the past.
Best regards,
Daniel
It's a limitation in Firefox for Android (fennec). It intentionally asks users each time.
It's being solved in the next generation version, available in beta as Firefox Preview (fenix). The prompt there adds this checkbox, similar to Firefox for desktop:
☐ Remember decision for this site
I am trying to build a Teams tab using an SPFx web part for a demo.
On my inital app the Sync to teams button in the app catalog was failing with this console error being returned...
https://{TENANT}/sites/AppCatalog/_api/web/tenantappcatalog/SyncSolutionToTeams 400
After running into this problem I started again and this time followed the below tutorial step by step but on my tenant the Sync to Teams button is disabled (This step is near in the end in the Making the web part available in Microsoft Teams section)
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/using-web-part-as-ms-teams-tab
I then tried to follow the alternative method of side-loading the app by creating a manifest manually using this tutorial...
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/creating-team-manifest-manually-for-webpart
This resuted in the installation succeeding as far as the setup tab screen (this provides a preview of your tab in a model popup before adding the tab to a channel)
The result was "Sorry, something went wrong" (This was the end result of side-loading both my customised web part another freshly yo sharepoint generated scaffold.
Really stuck on whether there's a tenant issue or maybe some node package or SPFx version issue.
Any thoughts would be greatly appreciated.
I received a same error from console which led me to this article.
In this case, the app was already synced to Teams store. If that's the case, you should find and remove it by opening Teams -> Apps -> Built for [tenantname]. After removing it here, I am able to successfully sync my app once more.
I'm using SPFx 1.8.1 version and added TeamsTab in supportedHosts manifest file. Deployed in tenant app catalog and tried to Sync to Teams. Then I'm getting same issue of SyncSolutionToTeams with 400 error. Please find the attached screenshot from console windwow.
The error occurs if the app is still in the Teams catalog. It doesn't override it and instead throws the error. This is a known bug and we will look to fix it in the future. For now, please try either manually updating the app from Teams (not from the SharePoint app catalog) or to delete the Teams app and then to resync from SharePoint.
In my case this error occurs when I changed title in webpart manifest file (webpart.manifest.json). When I rejected the change, it works. Probably there was some inconsistency in project files.
I am getting this error when I try to create a project in console.developers.google.com. I have 8 more projects left in my quota. I have tried different names and different project IDs. When I hit the "retry" button it shows the error after some time again.
UPDATE [Oct 9, 2017]: It looks like Google fixed the issue, since I was able to create a new project today.
I went ahead and attempted to create a new project in the Google API, and received the same error. This has occurred before with the Google API and is considered a temporary issue, often being fixed the same day. But if I remember correctly they have had it down longer in the past.
So the good news is, it's not something that is on your end, the bad news is, it's on Google's end.
If your google account is a Google Apps account (Google Suite, Google Apps, Gsuite, or whatever the Marketing folks are calling it these days), then you need to enable "Google Developers Console".
Login as an admin to admin.google.com
Go to Apps > Additional Google services
Find the "Google Developers Console" line item and set to "ON for everyone" (or whatever).
That should do it.
Ok, so without much notification given, adding market place listings to your vendor profile is no longer possible. The 'create new listing' button is greyed out.
I need to make changes to an existing marketplace listing but that gives errors. We are forced into the new SDK.
So I went ahead and enabled the apps market SDK, filled out all details including images of all sizes, add a COB extension for the contextual gadget and saved the whole thing.
A minute later I return to make a modification and dang... error: "We are looking into this.".
#Google: HELP !
UPDATE : I can reliably reproduce the error as explained here.
Enable Google Apps Marketplace SDK in your project
click on the gear icon, you will be directed to the old API Console
Fill out all details
Add a COB extension (Contextual gadget)
Save everything
Close the API console
Go back to your cloud console -> Google Apps Marketplace SDK
Click on the gear icon again
ERROR
Tested with several google accounts on different computeres and multiple projects on the cloud console.
#jonathanberi could we have a status on this issue, please? We are experiencing the exact same issue and we are unable to publish our app (which is ready) because of this bug. We have tried both creating a new Google Apps console project from scratch as well as modifying a draft of a yet to be published page with the same result. Is any information that we could provide to help?
You must fill out parameter name and a paramter value or your cloud console will return errors and you will not be able to recover from this.
Ouch, that were 3 useless weeks....
I'm currently working on a project that renders emails in HTML format to a Silverlight 5 app. The app is intended to be viewed via a web browser and not an 'Out of browser' app. The WebBrowser control was initially used, but I'm having issues with it. A message stating that IE needs elevated permissions and such. After reading how to properly implement the WebBrowser control by signing the .xap file and installing certificates it seems to work when I run it locally, but when I publish to the server (Windows Server 2008), it doesn't seem to work.
I tried to implement an alternative I found -> http://blogs.msdn.com/b/delay/archive/2007/09/10/bringing-a-bit-of-html-to-silverlight-htmltextblock-makes-rich-text-display-easy.aspx, but that didn't seem to work as the HTML I'm trying to render has many tags not supported in that example.
I also took a look at the Frame control http://msdn.microsoft.com/en-us/library/system.windows.controls.frame(v=vs.95).aspx but not sure if that would solve my problem either.
So if anyone can guide me into the right direction of either how I can get the WebBrowser control to work when pushed to the server or perhaps another alternative it would be greatly appreciated.