GitHub Community
Chrome #150397
Replies: 16 comments 2 replies
|
"STABLE |
|
Hi @vonidor01,
Let me know if you need further assistance! Best regards, |
|
Hi @vonidor01, Thank you for sharing your concerns. I understand how frustrating it can be when browser updates disrupt your workflow and affect the functionality of your apps and services. Let’s work through this step by step to find a solution. so, Chrome updates (specifically version 133) have caused issues with Google Voice, third-party apps, and in-app notifications. to Resolve
Go to Settings > Apps > Google Voice. Tap Storage > Clear Cache and Clear Data. Restart the app and log in again. Third-Party Apps: Check if the apps have pending updates in the Google Play Store. If updates are available, install them.
Open the Google Play Store. Search for “Chrome.” Tap the three-dot menu in the top-right corner and uncheck “Enable auto-update.”
Uninstall the current version of Chrome: Go to Settings > Apps > Chrome. Tap Uninstall (this will revert Chrome to the factory version). Download an older version of Chrome from a trusted source like APKMirror. Install the APK file and disable auto-updates as described above. Note: Reverting to an older version may expose you to security vulnerabilities, so use this as a temporary solution.
Open Chrome and type chrome://flags in the address bar. Search for the features listed in the update (e.g., Popover, WebGPU, CSS Scroll State Container Queries). Set these features to Disabled or Default. Restart Chrome.
Go to Settings > Network & Internet > Data Usage. Check which apps are consuming the most data. Restrict background data usage for Chrome and Google Play Store: Go to Settings > Apps > [App Name] > Mobile Data & Wi-Fi. Toggle off “Background data.”
Open Chrome and click the three-dot menu in the top-right corner. Go to Help > Report an issue. Describe the problem and include details about the affected apps and services.
Additional Notes If you’re considering legal action, I recommend consulting with your legal advisor to explore your options. Let me know if you need further assistance or if there’s anything else I can help you with! Best regards, |
|
"STABLE |
|
This is ridiculous |
|
Hi @vonidor01, I understand your frustration with the rapid updates and the impact on your workflow. Based on the features listed in Chrome 133, some experimental or newly enabled features (like Popover, WebGPU, or CSS Scroll State Container Queries) might be causing the issues. Here’s what you can do: 1.Disable Problematic Features: 2.Revert to Chrome 132: 3.Provide Feedback to Google: 4.Consider Alternative Browsers: Best regards, |
|
I've done all that. This still doesn't rectify issue. Can you please change
anything here that would possibly be causing data restrictions to apps.
…On Fri, Jan 31, 2025, 5:23 AM Aryan Arora ***@***.***> wrote:
Hi @vonidor01 <https://github.com/vonidor01>,
I understand your frustration with Chrome updates disrupting your apps and
services. Here’s a quick summary of steps to address the issue:
Update Apps: Ensure Google Voice and third-party apps are updated. Clear
their cache/data if needed.
Disable Chrome Updates: Temporarily stop Chrome auto-updates in the Google
Play Store.
Revert Chrome Version: Uninstall Chrome and install an older version from
a trusted source like APKMirror.
Disable Experimental Features: Go to chrome://flags and disable features
causing issues (e.g., Popover, WebGPU).
Monitor Data Usage: Restrict background data for Chrome and Google Play
Store in Settings > Apps > [App Name] > Mobile Data & Wi-Fi.
Provide Feedback: Report the issue via Chrome’s Help > Report an issue.
Try Alternative Browsers: Consider using Firefox, Brave, or Edge if issues
persist.
Let me know if you need further assistance!
Best regards,
Aryan.
—
Reply to this email directly, view it on GitHub
<#150397 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BN5Q5IUHP2NGQG7SEFGLNSL2NNFIPAVCNFSM6AAAAABWHHRP7SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRGYZTSMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi @vonidor01, Thank you for trying the suggested steps. Since the issue persists, let’s explore additional settings that might be causing data restrictions or app disruptions: Check Chrome’s Site Settings: Reset Chrome Settings: Review Data Saver/Storage Features: Check Network Restrictions: Test in Incognito Mode: If none of these steps resolve the issue, it might be worth reaching out to Google Support directly or considering a full reinstall of Chrome after backing up your data. Let me know if you need further assistance! Best regards, |
|
Could you please do it for me? I think I've suffered enough. I'm not
technical like that. The reason for me cheating this account in GitHub is
pacifically to express my disgrace for chrome.
…On Fri, Jan 31, 2025, 7:02 AM Aryan Arora ***@***.***> wrote:
Hi @axelopale <https://github.com/axelopale>,
Thanks for clarifying your goal! If you want to set the environment (e.g.,
staging, preprod, prod) once in the main workflow and make it accessible to
all sub-workflows, here’s how you can achieve this:
Solution: Use outputs to Pass Values to Reusable Workflows
Define the Environment in the Main Workflow:
Set the environment as a job output in the main workflow:
**yaml**
name: Deploy
on:
workflow_dispatch:
jobs:
set_env:
runs-on: ubuntu-latest
outputs:
environment: ${{ steps.set_env.outputs.environment }}
steps:
- name: Set environment
id: set_env
run: echo "environment=staging" >> $GITHUB_OUTPUT
build_js:
needs: set_env
uses: ***@***.***
with:
environment: ${{ needs.set_env.outputs.environment }}
Access the Environment in the Reusable Workflow:
In the reusable workflow (build_js_assets.yml), define the input and use
it:
*yaml on: workflow_call: inputs: environment: required: true jobs: build:
runs-on: ubuntu-latest steps: - name: Use environment run: echo
"Environment is ${{ inputs.environment }}"*
The set_env job sets the environment value and makes it available as an
output.
The build_js job passes this output to the reusable workflow via with.
This approach ensures the environment value is set once and reused across
all sub-workflows.
Optimization Tip:
If you have multiple reusable workflows, you can reuse the set_env job’s
output for all of them, avoiding redundancy.
Let me know if this meets your needs or if you need further assistance!
Best regards,
Aryan.
—
Reply to this email directly, view it on GitHub
<#150397 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BN5Q5ISXC2C2I6ZKJLCWXW32NNQ5JAVCNFSM6AAAAABWHHRP7SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRG4YTINI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Firebase Status Dashboard Updates</title>
<updated>2025-01-29T21:00:37+00:00</updated>
<link href="https://status.firebase.google.com/" rel="alternate"
type="text/html"></link>
<link href="https://status.firebase.google.com/en/feed.atom"
rel="self"></link>
<author>
<name>Firebase</name>
</author>
<id>https://status.firebase.google.com/</id>
<entry>
<title>RESOLVED: We're investigating high error rates for Chrome
Webpush by users of experimental versions of Chromium. We will provide
an update at 1 pm PST.</title>
<link href="https://status.firebase.google.com/incidents/76ERmF61vHoLxrg7cDNM"
rel="alternate" type="text/html"></link>
<id>tag:status.firebase.google.com,2025:feed:76ERmF61vHoLxrg7cDNM.FqEjsf2KcdWqLSXyeqCS</id>
<updated>2025-01-29T21:00:37+00:00</updated>
<summary type="html"><p> Incident began at
<strong>2025-01-21 00:00</strong> and ended at
<strong>2025-01-29 12:15</strong> <span>(all times
are <strong>US/Pacific</strong>).</span></p><div
class="cBIRi14aVDP__status-update-text"><p>The problem with
Chrome Webpush has been resolved. We apologize for the inconvenience
and thank you for your patience and continued support.</p>
</div><hr><p>Affected products: Cloud
Messaging</p></summary>
</entry>
</feed>
On Fri, Jan 31, 2025, 7:05 AM Von Johnson
***@***.***> wrote:
… Could you please do it for me? I think I've suffered enough. I'm not
technical like that. The reason for me cheating this account in GitHub is
pacifically to express my disgrace for chrome.
On Fri, Jan 31, 2025, 7:02 AM Aryan Arora ***@***.***>
wrote:
> Hi @axelopale <https://github.com/axelopale>,
>
> Thanks for clarifying your goal! If you want to set the environment
> (e.g., staging, preprod, prod) once in the main workflow and make it
> accessible to all sub-workflows, here’s how you can achieve this:
>
> Solution: Use outputs to Pass Values to Reusable Workflows
>
> Define the Environment in the Main Workflow:
> Set the environment as a job output in the main workflow:
>
> **yaml**
> name: Deploy
> on:
> workflow_dispatch:
> jobs:
> set_env:
> runs-on: ubuntu-latest
> outputs:
> environment: ${{ steps.set_env.outputs.environment }}
> steps:
> - name: Set environment
> id: set_env
> run: echo "environment=staging" >> $GITHUB_OUTPUT
> build_js:
> needs: set_env
> uses: ***@***.***
> with:
> environment: ${{ needs.set_env.outputs.environment }}
>
> Access the Environment in the Reusable Workflow:
> In the reusable workflow (build_js_assets.yml), define the input and use
> it:
>
>
>
>
>
>
>
>
>
>
>
> *yaml on: workflow_call: inputs: environment: required: true jobs: build:
> runs-on: ubuntu-latest steps: - name: Use environment run: echo
> "Environment is ${{ inputs.environment }}"*
>
> The set_env job sets the environment value and makes it available as an
> output.
> The build_js job passes this output to the reusable workflow via with.
> This approach ensures the environment value is set once and reused across
> all sub-workflows.
>
> Optimization Tip:
> If you have multiple reusable workflows, you can reuse the set_env job’s
> output for all of them, avoiding redundancy.
>
> Let me know if this meets your needs or if you need further assistance!
>
> Best regards,
> Aryan.
>
> —
> Reply to this email directly, view it on GitHub
> <#150397 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BN5Q5ISXC2C2I6ZKJLCWXW32NNQ5JAVCNFSM6AAAAABWHHRP7SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRG4YTINI>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***
> com>
>
|
|
Hi @vonidor01, I’m sorry to hear about the ongoing issues you’re facing with Chrome. Since you’ve already tried the suggested steps and the problem persists, let’s take a closer look at your specific situation. Unfortunately, I can’t directly access or modify your device settings, but I can guide you through the process step by step. Next Steps Disable Data-Restricting Features: Check App Permissions: Consider a Full Reinstall: If you’d like, I can provide detailed instructions for any of these steps. Let me know how I can assist further! Best regards, |
|
I just sent you a request. Can you please take over the account or join.
…On Fri, Jan 31, 2025, 7:07 AM Von Johnson ***@***.***> wrote:
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Firebase Status Dashboard Updates</title>
<updated>2025-01-29T21:00:37+00:00</updated>
<link href="https://status.firebase.google.com/" rel="alternate" type="text/html"></link>
<link href="https://status.firebase.google.com/en/feed.atom" rel="self"></link>
<author>
<name>Firebase</name>
</author>
<id>https://status.firebase.google.com/</id>
<entry>
<title>RESOLVED: We're investigating high error rates for Chrome Webpush by users of experimental versions of Chromium. We will provide an update at 1 pm PST.</title>
<link href="https://status.firebase.google.com/incidents/76ERmF61vHoLxrg7cDNM" rel="alternate" type="text/html"></link>
<id>tag:status.firebase.google.com,2025:feed:76ERmF61vHoLxrg7cDNM.FqEjsf2KcdWqLSXyeqCS</id>
<updated>2025-01-29T21:00:37+00:00</updated>
<summary type="html"><p> Incident began at <strong>2025-01-21 00:00</strong> and ended at <strong>2025-01-29 12:15</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p>The problem with Chrome Webpush has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.</p>
</div><hr><p>Affected products: Cloud Messaging</p></summary>
</entry>
</feed>
On Fri, Jan 31, 2025, 7:05 AM Von Johnson
***@***.***> wrote:
> Could you please do it for me? I think I've suffered enough. I'm not
> technical like that. The reason for me cheating this account in GitHub is
> pacifically to express my disgrace for chrome.
>
> On Fri, Jan 31, 2025, 7:02 AM Aryan Arora ***@***.***>
> wrote:
>
>> Hi @axelopale <https://github.com/axelopale>,
>>
>> Thanks for clarifying your goal! If you want to set the environment
>> (e.g., staging, preprod, prod) once in the main workflow and make it
>> accessible to all sub-workflows, here’s how you can achieve this:
>>
>> Solution: Use outputs to Pass Values to Reusable Workflows
>>
>> Define the Environment in the Main Workflow:
>> Set the environment as a job output in the main workflow:
>>
>> **yaml**
>> name: Deploy
>> on:
>> workflow_dispatch:
>> jobs:
>> set_env:
>> runs-on: ubuntu-latest
>> outputs:
>> environment: ${{ steps.set_env.outputs.environment }}
>> steps:
>> - name: Set environment
>> id: set_env
>> run: echo "environment=staging" >> $GITHUB_OUTPUT
>> build_js:
>> needs: set_env
>> uses: ***@***.***
>> with:
>> environment: ${{ needs.set_env.outputs.environment }}
>>
>> Access the Environment in the Reusable Workflow:
>> In the reusable workflow (build_js_assets.yml), define the input and use
>> it:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *yaml on: workflow_call: inputs: environment: required: true jobs:
>> build: runs-on: ubuntu-latest steps: - name: Use environment run: echo
>> "Environment is ${{ inputs.environment }}"*
>>
>> The set_env job sets the environment value and makes it available as an
>> output.
>> The build_js job passes this output to the reusable workflow via with.
>> This approach ensures the environment value is set once and reused
>> across all sub-workflows.
>>
>> Optimization Tip:
>> If you have multiple reusable workflows, you can reuse the set_env job’s
>> output for all of them, avoiding redundancy.
>>
>> Let me know if this meets your needs or if you need further assistance!
>>
>> Best regards,
>> Aryan.
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#150397 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/BN5Q5ISXC2C2I6ZKJLCWXW32NNQ5JAVCNFSM6AAAAABWHHRP7SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRG4YTINI>
>> .
>> You are receiving this because you were mentioned.Message ID:
>> ***@***.***
>> com>
>>
>
|
|
… On Fri, Jan 31, 2025, 7:13 AM Von Johnson ***@***.***> wrote:
I just sent you a request. Can you please take over the account or join.
On Fri, Jan 31, 2025, 7:07 AM Von Johnson ***@***.***> wrote:
> <?xml version="1.0" encoding="UTF-8"?>
> <feed xmlns="http://www.w3.org/2005/Atom">
> <title>Firebase Status Dashboard Updates</title>
> <updated>2025-01-29T21:00:37+00:00</updated>
> <link href="https://status.firebase.google.com/" rel="alternate" type="text/html"></link>
> <link href="https://status.firebase.google.com/en/feed.atom" rel="self"></link>
> <author>
> <name>Firebase</name>
> </author>
> <id>https://status.firebase.google.com/</id>
> <entry>
> <title>RESOLVED: We're investigating high error rates for Chrome Webpush by users of experimental versions of Chromium. We will provide an update at 1 pm PST.</title>
> <link href="https://status.firebase.google.com/incidents/76ERmF61vHoLxrg7cDNM" rel="alternate" type="text/html"></link>
> <id>tag:status.firebase.google.com,2025:feed:76ERmF61vHoLxrg7cDNM.FqEjsf2KcdWqLSXyeqCS</id>
> <updated>2025-01-29T21:00:37+00:00</updated>
> <summary type="html"><p> Incident began at <strong>2025-01-21 00:00</strong> and ended at <strong>2025-01-29 12:15</strong> <span>(all times are <strong>US/Pacific</strong>).</span></p><div class="cBIRi14aVDP__status-update-text"><p>The problem with Chrome Webpush has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.</p>
> </div><hr><p>Affected products: Cloud Messaging</p></summary>
> </entry>
> </feed>
>
> On Fri, Jan 31, 2025, 7:05 AM Von Johnson
>
> ***@***.***> wrote:
>
>> Could you please do it for me? I think I've suffered enough. I'm not
>> technical like that. The reason for me cheating this account in GitHub is
>> pacifically to express my disgrace for chrome.
>>
>> On Fri, Jan 31, 2025, 7:02 AM Aryan Arora ***@***.***>
>> wrote:
>>
>>> Hi @axelopale <https://github.com/axelopale>,
>>>
>>> Thanks for clarifying your goal! If you want to set the environment
>>> (e.g., staging, preprod, prod) once in the main workflow and make it
>>> accessible to all sub-workflows, here’s how you can achieve this:
>>>
>>> Solution: Use outputs to Pass Values to Reusable Workflows
>>>
>>> Define the Environment in the Main Workflow:
>>> Set the environment as a job output in the main workflow:
>>>
>>> **yaml**
>>> name: Deploy
>>> on:
>>> workflow_dispatch:
>>> jobs:
>>> set_env:
>>> runs-on: ubuntu-latest
>>> outputs:
>>> environment: ${{ steps.set_env.outputs.environment }}
>>> steps:
>>> - name: Set environment
>>> id: set_env
>>> run: echo "environment=staging" >> $GITHUB_OUTPUT
>>> build_js:
>>> needs: set_env
>>> uses: ***@***.***
>>> with:
>>> environment: ${{ needs.set_env.outputs.environment }}
>>>
>>> Access the Environment in the Reusable Workflow:
>>> In the reusable workflow (build_js_assets.yml), define the input and
>>> use it:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *yaml on: workflow_call: inputs: environment: required: true jobs:
>>> build: runs-on: ubuntu-latest steps: - name: Use environment run: echo
>>> "Environment is ${{ inputs.environment }}"*
>>>
>>> The set_env job sets the environment value and makes it available as an
>>> output.
>>> The build_js job passes this output to the reusable workflow via with.
>>> This approach ensures the environment value is set once and reused
>>> across all sub-workflows.
>>>
>>> Optimization Tip:
>>> If you have multiple reusable workflows, you can reuse the set_env
>>> job’s output for all of them, avoiding redundancy.
>>>
>>> Let me know if this meets your needs or if you need further assistance!
>>>
>>> Best regards,
>>> Aryan.
>>>
>>> —
>>> Reply to this email directly, view it on GitHub
>>> <#150397 (comment)>,
>>> or unsubscribe
>>> <https://github.com/notifications/unsubscribe-auth/BN5Q5ISXC2C2I6ZKJLCWXW32NNQ5JAVCNFSM6AAAAABWHHRP7SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRG4YTINI>
>>> .
>>> You are receiving this because you were mentioned.Message ID:
>>> ***@***.***
>>> com>
>>>
>>
|
|
i cannot access the repos with this as An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see GitHub Deceased User Policy. i can guide you through the steps if you are having any trouble. |
|
Ok
…On Fri, Jan 31, 2025, 7:19 AM Aryan Arora ***@***.***> wrote:
i cannot access the repos with this as An appointed successor can manage
your public repositories after presenting a death certificate then waiting
for 7 days or presenting an obituary then waiting for 21 days. For more
information, see GitHub Deceased User Policy
<https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>
.
i can guide you through the steps if you are having any trouble.
—
Reply to this email directly, view it on GitHub
<#150397 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BN5Q5IUJNPKYUALB7ODDTZT2NNS6XAVCNFSM6AAAAABWHHRP7SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRG4ZDONI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
chrome://settings/reset.
I can't
…On Fri, Jan 31, 2025, 7:13 AM Aryan Arora ***@***.***> wrote:
Hi @vonidor01 <https://github.com/vonidor01>,
I’m sorry to hear about the ongoing issues you’re facing with Chrome.
Since you’ve already tried the suggested steps and the problem persists,
let’s take a closer look at your specific situation. Unfortunately, I can’t
directly access or modify your device settings, but I can guide you through
the process step by step.
Next Steps
Reset Chrome Completely:
Go to chrome://settings/reset.
Click “Restore settings to their original defaults.”
Confirm the reset. This will clear all settings, extensions, and cached
data without affecting your bookmarks or saved passwords.
Disable Data-Restricting Features:
Go to chrome://settings/performance.
Turn off “Memory Saver” and “Energy Saver.”
Go to chrome://settings/privacy and disable “Enhanced Protection.”
Check App Permissions:
Go to chrome://settings/content.
Ensure permissions for notifications, microphone, and storage are enabled
for Google Voice and other affected apps.
Reach Out to Google Support <https://support.google.com/chrome/>:
Visit Google Support and explain your issue in detail.
Provide them with the error logs or screenshots of the problem.
Consider a Full Reinstall:
Back up your Chrome data (bookmarks, passwords, etc.).
Uninstall Chrome completely.
Reinstall Chrome from the official website: Download Chrome
<https://www.google.com/chrome/>.
If you’d like, I can provide detailed instructions for any of these steps.
Let me know how I can assist further!
Best regards,
Aryan
—
Reply to this email directly, view it on GitHub
<#150397 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BN5Q5IVASGMYZBH5J7GKKUD2NNSHJAVCNFSM6AAAAABWHHRP7SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRG4ZDGNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
They have me restricted.
…On Fri, Jan 31, 2025, 7:26 AM Von Johnson ***@***.***> wrote:
chrome://settings/reset.
I can't
On Fri, Jan 31, 2025, 7:13 AM Aryan Arora ***@***.***>
wrote:
> Hi @vonidor01 <https://github.com/vonidor01>,
>
> I’m sorry to hear about the ongoing issues you’re facing with Chrome.
> Since you’ve already tried the suggested steps and the problem persists,
> let’s take a closer look at your specific situation. Unfortunately, I can’t
> directly access or modify your device settings, but I can guide you through
> the process step by step.
>
> Next Steps
> Reset Chrome Completely:
> Go to chrome://settings/reset.
> Click “Restore settings to their original defaults.”
> Confirm the reset. This will clear all settings, extensions, and cached
> data without affecting your bookmarks or saved passwords.
>
> Disable Data-Restricting Features:
> Go to chrome://settings/performance.
> Turn off “Memory Saver” and “Energy Saver.”
> Go to chrome://settings/privacy and disable “Enhanced Protection.”
>
> Check App Permissions:
> Go to chrome://settings/content.
> Ensure permissions for notifications, microphone, and storage are enabled
> for Google Voice and other affected apps.
> Reach Out to Google Support <https://support.google.com/chrome/>:
> Visit Google Support and explain your issue in detail.
> Provide them with the error logs or screenshots of the problem.
>
> Consider a Full Reinstall:
> Back up your Chrome data (bookmarks, passwords, etc.).
> Uninstall Chrome completely.
> Reinstall Chrome from the official website: Download Chrome
> <https://www.google.com/chrome/>.
>
> If you’d like, I can provide detailed instructions for any of these
> steps. Let me know how I can assist further!
>
> Best regards,
> Aryan
>
> —
> Reply to this email directly, view it on GitHub
> <#150397 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BN5Q5IVASGMYZBH5J7GKKUD2NNSHJAVCNFSM6AAAAABWHHRP7SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBRG4ZDGNA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***
> com>
>
|
|
Hi @vonidor01, Thanks for being a part of the GitHub Community, we're glad you're here! If you're looking for help for this specific topic, you might want to try asking for help somewhere that focuses on this project, such as the Google Chrome Support. It's possible that another GitHub user might have run into this same issue and can help, but the GitHub Community Discussions focuses primarily on topics related to GitHub itself or collaboration on project development and ideas. We want to make sure you’re getting the best support you can, but this space may not be the right place for this particular topic. Best of luck! |
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
General
Body
I'm so disappointed. Chrome keeps implementing features in chrome status that's causing my other apps and service not to work. My Google voice, and third party apps aren't functioning. I'm not receiving any in app notifications. Only Google play store, Google play store, and chrome are accumulating mass amounts of data. Is it possible to regress from what they have done. What's ironic is they don't consider how these roll out affect my daily process. Just implementing the dump features without consideration that it's changing behavior on my phone. They went from 130 to 133 within a week. I'm sick of it. I've already contacted a law office for litigationa
All reactions