If the app makes a call to brainCloud that timeouts, it will generate a CLIENT_NETWORK_ERROR_TIMEOUT (90001) error in the failure callback.

_bc.EntityService.GetEntitiesByType(entityType,
    (string response, object cbObject) =>
    {
      Debug.Log("SUCCESS");
    },
    (int statusCode, int reasonCode, string statusMessage, object cbObject) =>
    {
      switch (reasonCode)
      {

        case ReasonCodes.CLIENT_NETWORK_ERROR_TIMEOUT:
          {
            // Handle the timeout 
            break;
          }
      }
    });

The brainCloud SDK will timeout after a set interval. Currently, in the 4.2 release, the default is 35 seconds, but this may be adjusted later.

You can also call SetPacketTimeouts to set a custom amount for your timeout values. But the defaults are recommended.

An example of handling a timeout error in Unity can be found in our AuthenticationErrorHandling example.

This error has been since resolved.

A help article has been made on the groupType page: http://help.getbraincloud.com/en/articles/3272656-design-groups-group-types

If experience similar problems to this forum topic with our Unity library, ensure brainCloud has been added to a gameObject, and that gameObject is not disabled.

The fix will be going into the 4.2 patch on Tuesday. (Sept 17th) - now Wednesday Sept 18th.

Thanks for reporting the issue. A developer has been assigned the issue and is working on the fix. We will let you know when it's live

As an interim solution, you can add a cloud code script or a post-hook to retrieve the missing data, using the profileIds found in the request.

https://getbraincloud.com/apidocs/apiref/#capi-friend-getsummarydataforprofileid

  ...
  "pendingMembers": {
    "382eb04f-f80c-4bfc-9a12-fca508cad476": { // <- These profile ids
      "role": "MEMBER",
      "attributes": {},
      "pendingReason": "ASKED_TO_JOIN"
    }
  }
  ...

I am forwarding this to the devs to look into addressing.

Hey,

The GetMyGroups will return the group requests and invites made to the current profile.

As you noticed, to get the requests and invites made to a group (from other profiles), you need to use ReadGroup.

This flow is working as intended. Groups and profiles are separate objects, and both can make invites and receive requests.

So using GetMyGroups: here would be an example of a user that has made a group request, and has received a group invite.

{  
   "data":{  
      "requested":[  
         {  
            "groupType":"DiscussionGroup",
            "groupId":"ad1ae126-d030-4d21-92c5-3e9d0b959647",
            "memberCount":1,
            "name":"Dark Roast",
            "invitedPendingMemberCount":0,
            "requestingPendingMemberCount":1,
            "ownerId":"f86a20d4-51a3-4594-a5b0-90111bf55e6d",
            "isOpenGroup":false
         }
      ],
      "invited":[  
         {  
            "groupType":"DiscussionGroup",
            "groupId":"b1d958e3-d196-45e2-9567-8efeb3296482",
            "memberCount":1,
            "name":"Local Coffee Shops",
            "invitedPendingMemberCount":1,
            "requestingPendingMemberCount":0,
            "ownerId":"f86a20d4-51a3-4594-a5b0-90111bf55e6d",
            "isOpenGroup":true
         }
      ],
      "groups":[  

      ]
   },
   "status":200
}

Hope that helps!

You could also create a Global Property that houses your shared code.

Properties can be set on the Design | Custom Config | Global Properties page.

function getFuzz() {
    return 'Fuzz';
}

function addTwoNums( a, b ) {
    return a + b;
}

And use the bridge to get the shared code via bridge.getGlobalProperty("sharedScripts").

Example:

var response = {};

// First Load the shared scripts into a string object
var sharedScripts = String(bridge.getGlobalProperty("sharedScripts"));

// Output to the log - helps for debugging. Debug log is only written to when run from API explorer or CC editor
bridge.logDebug("Loading shared code...", sharedScripts);

// And now evaluate the functions so that they become part of the script.
// Any errors in the code being evaluated will be reported as errors as if they
// occurred in the script itself. This affects the line numbers the error is reported upon.
eval(sharedScripts);

// Now you can use any of the functions included...
response.getFuzz = getFuzz();
response.sum = addTwoNums( 5, 10 );

response;

This has been tested with up to 30k bytes of code.
That said, isn't an officially sanctioned approach. We don't recommend putting more than 20-25kb in the shared code string.

Unfortunately not really.

You can call cloud code scripts from cloud code scripts (via the bridge.callScript() method).

Otherwise, people have also just copied and pasted shared code at the top of their scripts.

If it is a cert issue. These steps may help: https://www.mobiloud.com/help/knowledge-base/how-to-export-push-notification-certificate-p12/

edit: this link seems to confirm the cert theory. Based on the error message: https://stackoverflow.com/questions/22568648/ios-production-push-notifications-invalid-token-from-apns-server