The somewhat-new feature of bot menu button now dissapeared from my and other bots I used from my macOS client, presumably after latest mac Telegram update, version 8.1 (221723) Stable. Looking at some screenshots I did, menu button was there as of 14th September. Still shows on the Android phone. Link to two screenshots showing the issue
Google and SO searches do not address the question:
Can developers manage the appearance of the menu button instead of attachment button? Where did it go?
My bot heavily depends on the button and doesn't give any hints to the commands in the text. Did they silently disable it for desktop client? Any insight appreciated.
Can developers manage the appearance of the bot-menu button?
Yes, by using the setMyCommands method, you can control the command listed in the menu.
The command scope is used to determine the list of commands for a particular user viewing the bot menu
Can developers manage the appearance of the attachment-menu button?
No, the attachment button is handled by the Telegram Client.
Therefore it's not possible to manually show/hide the button.
There isn't a complete list of clients which will show the button, however
Telegram Desktop 3.1 client
Telegram 8.1 (221723) AppStore client
Both show the original design, with the / and attachment button.
The Android version does not show the button.
Related
I would like to disable efr param to 1 in our dynamic link from firebase, in order to skip the preview page and get directly to the appstore. Thinking it will work.. but now the link is not copied to the app on install. What is your solution here in order to not show the preview page, go directly to the appstore, and keep the url within the clipboard on install?
IMO, UX wise, it's nicer to not have the preview page, even if I add metadata to it.
Thanks.
While there's an option to disable the app preview page, it's in place to ensure Dynamic Link reliability in iOS. You can have it disabled, but it won't guarantee that the FDL will work as expected in iOS. This is explained in more detail here.
I am in trouble with the operation of Progressive Web Apps.
First, I pressed "Add to Home Screen" on the web, added the application to the home screen, and gave permission for push notification.
After that, I uninstalled Progressive Web Apps from the home screen, I expected that the notification will not arrive, but in fact it gets notified.
Can I detect uninstallation and reject push notifications?
I tried searching including the following site.
For example, but there is nothing expected of event or status.
Although it is an attachment of the home screen after uninstallation,
A Google Chrome icon is displayed in the notification bar.
home screen image
Based on your comment in response to the other answer, I figure you are building a progressive web app and want to implement this feature (turning off notifications on removal from the home screen) in your own PWA?
Currently (October 2017) there is no way for a PWA to detect if a user has removed it from their home screen. There is a way for the PWA to detect if it is uninstalled (as in the service worker is removed from the browser all together) but that is something totally different. You aren't uninstalling the PWA when you remove it from the home screen, you're just removing a shortcut. The PWA is still installed in the user's browser. They could still manually visit the site and your PWA would still be working.
Maybe this will become a feature in the future. For right now there isn't even a way to create a hack that would help.
If you navigate to the web app in question using Chrome for Android, either directly or by tapping on a notification, you can manually adjust its permissions by tapping on the "Lock" icon next to the location bar, then choosing "SITE SETTINGS", and then making changes there.
The specific steps to do this would vary if you're using a browser other than Chrome.
The docs here https://developers.google.com/+/mobile/android/share/deep-link seem to be hopelessly out of date, as I cannot find any of the mentioned (like "Edit settings").
Can somebody provide some guidance on how to make a deep link to my app work from within a Google+ post?
e.g., I would expect a link such as "appname://?id=12345678" to be a clickable thing that directs the user either to install the app or opens the installed app and takes the user directly to the content specified by the id. Instead, this link is posted as plain text...
Moreover, will I need to fight with every social network to get deep links to work properly? Does anybody have any experience making this sort of thing work on Twitter, Facebook, etc?
We are developing with Meteor, and using the Cordova cordova-plugin-x-socialsharingplugin https://github.com/EddyVerbruggen/SocialSharing-PhoneGap-Plugin
You may want to try using App Invites, which either will let the app receive data from the invitation if the app is already installed (e.g. a coupon) or will install the app.
From an official account main menu view I can provide a URL and it will open in the built in WeChat browser.
Is there a way to close the browser and come back to the main account menu?
I don't want to have the user hit the [X] button each time.
Is there a standard URL format for an official account that can be used as a link to open the account from a browser?
In short, there's no way to do that.
In early days, there are some hacking ways to do this, but now they are all not working any more.
You can put a qrcode image of your account on your site for users to scan and follow you.
When my activity is running, I don't want return in home screen when I click on Home button.
I find answers for android but I do not manage to translate code to mono.
Can you help me please ?
Disabling the home button is an anti-pattern and generally frowned upon in Android. You are not able to override the behavior of the Home button itself in ICS and up either. However if you are developing a Kiosk mode app or a Home launcher, it is possible to work it around.
You will need to tell Android that your application is a Launcher/Home application. Beyond creating a custom home app, there is no way to intercept the HOME button except through firmware modifications.