Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation out of date for PlayFab and SignalR setup #47

Open
ivandamyanov opened this issue May 3, 2020 · 2 comments
Open

Documentation out of date for PlayFab and SignalR setup #47

ivandamyanov opened this issue May 3, 2020 · 2 comments

Comments

@ivandamyanov
Copy link

Instructions not clear... I created a remote controlled missile execution platform.

Jokes aside, first issue is with the connection string for this sample:
https://github.com/PlayFab/PlayFab-Samples/tree/master/Samples/CSharp/MessagingClient

"4. Open the local.settings.json file in the PlayFab.SignalRSample project in this repo"
That is not enough. After publishing the functions, they throw errors that there's no SignalR connection string. I manually added it from the Azure Portal in the "Configure" section of the function. The error went away. I guess that's related to other documentation being out of date for more or less a year: MicrosoftDocs/azure-docs#28140

The second issue:
"Repeat steps 3-10 using Name=Matchmaking Notifications, Event type=playfab.matchmaking.match_found, and Function=MatchFound"

This event is no longer found as a trigger: "playfab.matchmaking.match_found".
I found this comment "https://community.playfab.com/questions/35040/cannot-add-rule-for-event-matchmaking-match-found.html"

@amccalib
Copy link
Contributor

I'll take a look at the first issue. As to the second, it looks like the match_found event isn't available to trigger cloud script for all titles. It's actually part of a limited preview. If you want to be added while it's still in preview, let me know.

@amccalib
Copy link
Contributor

amccalib commented Jul 31, 2020

I fixed the documentation to account for the first issue. Still waiting on the Azure Function trigger to be made fully public to address the second.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants