I built my bot using Bot Framework Composer 2.1 and everything looked nice in the design process, however, when I was about to publish it I got the following message:
Provision failure
{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n at new CustomizeError (\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:269071:25)\n at createCustomizeError (\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:269076:10)\n at BotProjectProvision.createApp (\\resources\\app.asar.unpacked\\extensions\\azurePublish\\dist\\extension.js:270566:17)"}. See provision.botazure.log in your bot folder
Anyone happens to know how to sort this issue out?
This is a bug and is being tracked here.
Related
Has someone been able to connect a composer bot with Direct Line Extension . The code and samples apply only to SDK and cant find a sample for Composer and the current ones are not working within Composer bots ?
I have checked with Microsoft and the directline app service extension with bot composer feature request is not enabled yet.
Something to look is below but that will be a custom solution :
https://learn.microsoft.com/en-us/composer/concept-extend-with-code
I recently updated my app.yaml from
runtime: go114
to
runtime: go115
because I was warned in an email that support for go114 was ending.
The service deployed fine but after it finished, I got the message:
Updating service [default]...â ¼WARNING: There is an indirect dependency on App Engine APIs, but they are not enabled in your app.yaml. You may see runtime errors trying to access these APIs. Set the app_engine_apis property.
So I added:
app_engine_apis: true
And now the service won't deploy and gives this error:
ERROR: (gcloud.app.deploy) An error occurred while parsing file: [<snip>/app.yaml]
Unexpected attribute 'app_engine_apis' for object of type AppInfoExternal.
Looks like a catch 22. How do I deal with this?
Posting this as community wiki as it's based on #Joel's comments.
It looks like this is being triggered, since those APIs aren't enabled yet in go115, you might get a runtime error.
I would say that you should probably reach out to Google Cloud either in their Issue Tracker system or open an Issue in this Github Page so that they can fix this issue, as there doesn't seem to be any workarounds for this one.
I had push notifications working some time ago, but it is not working anymore.
Is there any issue with Android 8.0?
I did not change the AndroidManifest.xml since the last working version and I checked up the http://docs.gluonhq.com/samples/pushnotes example again.
When sending the message and running the logcat I get the following error message:
No Channel found for pkg=[myPackageName], channelId=null, id=123456, tag=null, opPkg=[myPackageName], callingUid=10298, userId=0, incomingUserId=0, notificationUid=10298, notification=Notification(channel=null pri=2 contentView=null vibrate=default sound=null defaults=0x2 flags=0x10 color=0x00000000 category=event vis=PUBLIC)
This one too:
The Google Play services resources were not found. Check your project configuration to ensure that the resources are included
Any help appreciated!
Updated to Parse SDK 1.7.1 with Bolts 1.1.4 and using the new and latest Facebook SDK. Every time I login the user I get the following error:
[BFTask isFaulted]: unrecognized selector sent to instance error.
I'm able to login the user, the user's info is store in parse, but not sure how to resolve this exception.
Anyone else having this problem?
Had this problem also.
I copied the Parse Bolts framework to the project directory. Referencing didn't do it. Same for Parse FacebookutilsV4.
I had solved this problem just a minute ago.
You need update the latest FacebookSDK to avoid this error.
You can just download the latest SDK from facebook website.
However if you just drag the parse and facebook framework together into the project, maybe a 'duplicate' error will be reported.
So I recommend you to use CocoaPods to manage your thirdparty framework.
I m using Eclipse plugin to deploy new application on Heroku. However recently when I m trying to create a new app I get the following exception from Eclipse at the stage where I select a template app:
An unknown error has occurred. If this error persists, please follow up with Heroku support.
com.heroku.api.exception.RequestFailedException: Unexpected app exist status statuscode:401 responseBody:{"id":"unauthorized","error":"Unauthorized"}
I understand that it has to do with authorization. However I cannot find the way to check my credentials that I have provided to the Eclipse plugin. As far as I remeber the credentials are given during the next step , once you have selected and named your template app.
Anybody knows if there is a problem with eclipse plug in for heroku?
Thank you.