Questions
When sending an AppRequest, my friends list that comes up on iOS always has 48 users in it even when I have 300+ friends. Is there a way to change this limit for high-end devices that have plenty of memory?
How does FB decide which 48 friends to show in the AppRequest dialog? It doesn't appear to be my first 48 friends alphabetically
The "Title" parameter of the AppRequest call doesn't get used. Even in the InteractiveConsole, I set the title to "Invite Friends" and the title always says "App Requests". Is this just broken or am I confused?
Edit: I know there is a maxRecipients param but my understanding is that only determines how many total can be SENT at once, not how many friends display. I have the maxRecipients set at 500 and it still only shows 48 friends in the list.
Info
Unity version: 4.3.0f4
FB SDK version: 4.3.4
FB Build version: 131022.2bb3e6026790434
Right now there's no way to change the number of users who come up in that selector. They're chosen according to Facebook's estimate of how likely they are to be interested in, and interact with, an apprequest.
I believe that the issue with the title may be a bug. I'm investigating that now; could you please file a bug in the FB developer bug tool, and post the URL here, to help with that?
Related
https://apps.microsoft.com/store/detail/name/ID
Linking to my app product page gives "Not Available for bots to index"
What is the proper syntax to place a href link to the product so that users online can view it as html?
I don't have a final solution, just a workaround.
We've been seeing the same issue with our own app for the past few days and we've started seeing reports of people encountering this with all kinds of apps, including even Microsoft's own AppInstaller. It seems to be a server-side rate-limiting/caching issue at Microsoft as changing anything in the URL fixes the problem temporarily -- only to get back to the same issue a few hours later. We also found that VPN-ing to some locations (mostly to the US) helped as well, and this throttling seems to be specific to an app & an availability region (when it got blocked, it blocked across all Europe, but not in US for example). It seems to come & go as we have not seen a big drop in new install counts.
As a temporary solution we ended up adding a random string to the end of the URL. We used GCLID as we found it to be the least offensive way -- it could just as well be a legitimate tracking ID we pass over. So now the URL we link to looks like this:
https://apps.microsoft.com/store/detail/[APPNAME]/[APPID]?gclid=f-3579a28842a7bcac7ba630d698829e9b
Where the "f-xxxx" value is generated using the md5() of the timestamp -- but it could be any ever-changing value, even a random number.
We've reached out to our MS contact about this but we haven't heard back yet.
I encountered the same issue half an hour ago, but it seems recovered now.
If you own an app, you can confirm Product identity in Partner Center:
You can share the direct link and Store ID to help customers find your app in the Store:
URL: https://www.microsoft.com/store/apps/*12CharsAppId*
Store ID: 12CharsAppId
Store protocol link: ms-windows-store://pdp/?productid=12CharsAppId
The above address would be recommended but the apps.microsoft.com URL should also work.
I work on apps.microsoft.com. I can confirm that there was an issue on our end that appeared on August 23. This issue has been resolved.
And the proper link, of course, is this:
https://apps.microsoft.com/store/detail/[your product id here]
I have been playing around with One Signal & Firebase Push Notification.
I am almost sure One Signal cannot help me and am starting to feel Firebase might also not be able to help me.
We have a web app that allows regular authors to post articles. It also allows users to comment on the article using Firebase synced realtime database.
I want to create functionality where users can get a push notification for article-specific comment treads. The room ID will be the article ID. If both allow push notification generally from our app and has commented on an article, they subscribe to this article comment tread solely. They can also click a button at this specific article comment thread and unsubscribe to this article comment thread if they want.
So we may have thousands of articles and hundreds of comments in each article, to put it lightly.
I quickly moved away from One Signal when I didn't feel like I could have a separate "Segment" for each article, I wasn't certain this is allowed? Thoughts there?
Throughout my exploration of Firebase I just came across this comment in their documentation in relation to groups (Which I was hoping could be my article room).
"The maximum number of members allowed for a notification key is 20" found here. A key is a group key from my understanding. This won't work because what if there are more than 20 users in a comment thread. I looked up the most popular commented threads ever to find numbers like 500. This means my system would have to be able to support large numbers of users per article tread.
Additionally One Signal Tags and Social activities look like could be investigated, but my general question is not specific, its more a wider general question. I am hoping someone with experience can give some guidance and good tips on best way to approach this problem. Are Push notification even allowed on such a scale I am wondering?
A scaling examples
1000 Articles with 100s of different users commenting on each article. A user may only receive a push notification on articles which he has commented in only.
(Assuming he has allowed push notification site-wide first and not blocked us or unsubscribed from the site entirely. Subscribing to the site doesn't automatically subscribe you to anything specific, just means you willing to be subscribed to something and have control which things easily)
Ok thanks for reading and looking forward to hearing from someone with this experience and share their experience.
Daniel Gadd # GaddBox
Maybe it's a bit late.
You have to use topics.
FCM topic messaging allows you to send a message to multiple devices that have opted in to a particular topic. You compose topic messages as needed, and FCM handles routing and delivering the message reliably to the right devices.
In your case, every Article is a topic.
I'm getting an error for a survey that has about 90 questions but only 10 respondents when I try to use the Smartsheet Sync add on. Error says that it"Exceeds Maximum Execution Time". How can I increase the execution time so that it will add responses to my Smartsheet? I don't know anything about coding. I'm not evens sure if I could edit the add-on? Please advise.
Thanks for sharing your form with me, so that I could take a closer look. It appears that your form actually contains 96 sections each with multiple questions. When you create a Google Sheet for the form responses, 361 columns are created.
This is probably the cause of your issue. Each sheet in Smartsheet can only handle around 200 columns per sheet, and Smartsheet Sync automatically tries to create a column for each question in your Google Form. It appears you have uncovered a bug where our error messaging in Smartsheet Sync could be better - informing the user that the form has more questions than a sheet can handle, rather than trying to create the sheet and then timing out. We will make a note of this bug so that we can address it in a future revision.
As it stands, Smartsheet would not be able to handle a form with 361 questions, so it doesn't appear that Smartsheet Sync will be able to handle this form.
We were checking newly implemented Google Analytics for our mobile app and surprisingly there are a lot of visitors from multiple countries but in actuality, we haven't released our app for any store and it's just beta between 5 main users.
After checking Google Analytics report in details we have found that it got spammed by Bot call "Trumps Bot" when something happens on your account you can see following lines in your language section.
“Secret.ɢoogle.com You are invited! Enter only with this ticket URL. Copy it. Vote for Trump!”
There are a lot of solution available to avoid this data in your reports using the filter but i was just wondering if there is any concrete solution on permanently remove this data from my reports and also is there anything we can do to avoid such data in future as its seriously affecting business strategy.
Due the tecnology used on Google Analytics the only way to eliminate this referal is using a filter, check one common point of all this hits . In this case is a hard one, because all the parameters changes , exept for the language, for a well know reason, to see the spam.
So try to use this one, in my case works
I highly recommend you read the community policy, this can be considered as off-topic question
Analytics spammers are always trying to find new ways of getting attention, and with this one, this spammer hit it big.
It is not possible to permanently remove it unless you delete the whole property. But you can create and advance segment to get a clean view.
But the most important part is blocking it so it doesn't pollutes your data. For this particular type of spam you should create a custom exclude language filter with this expression:
\s[^s]*\s|.{15,}|.|,
That expression will block any hit that doesn't use a proper language. That combined with a valid hostname filter should prevent most of the current spam and save you a lot of headaches.
If you need help, you can check this step by step guide for building these filters and creating the advanced segment to remove it from your historical data.
Here is also a related question.
Login in to Your Google Analytics account
Select ADMIN Section
Click on All Filters -- Add Filters
Give a filter name such as -- Include only website traffic
In Predefined section, select Include Only
for more... Click Here
I am trying to fetch as many LinkedIn updates as possible for a company--
Here is the link I am using -
https://api.linkedin.com/v1/companies/21837/updates?event-type=status-update&count=250
But it only returns 10 updates. There are many more updates but they don't show up in the response. All posts older than a month ago don't show up. Is there a limitation on how far back you can go?
Appreciate any help!
20 days seems to be the limit, according to the LinkedIn API documentation.
Note that the API returns the latest 50 updates only for event type
status-update. If you have updates of other types (such as jobs
posting, product-updates etc.) then it can fetch up to 250 updates or
updates in the last 20 days whichever comes first.
The wording there isn't totally clear, their API documentation isn't very good unfortunately.