Strange issue with Strike Select Component that clearing browser history/cache fixed

[cnaccio]

Hey guys,

One of my apps that's using the Strike Select Component started having random/intermittent errors lately. Through some troubleshooting I've discovered that clearing the browser cache resolved the problem. I was having the problem in both Chrome and IE Edge.

If you guys can help provide any guidance, I'd sure appreciate it. I'm planning on upgrading to the latest version of the strike components as I'm currently on v0.9.0 but I'd really like to have a better idea of what's going wrong so that I'm not stabbing in the dark. Thanks in advance!

The problem seems to be related to the function below in the strike_selectHelper.js file; specifically the component.get('v.body').forEach line.

getChildOptions: function(component, event, helper) {
        var options = [];

        component.get('v.body').forEach(function(child) {
            if ($A.util.isUndefined(child.select)) {

                var childOptions = helper.getChildOptions(child, event, helper);

                options = options.concat(childOptions);
            } else {
                options.push(child);
            }
        });

        return options;
}

Here's a screenshot of the error:

[daneowens3]

hello @cnaccio this is happening on page load? being three versions back makes it a little hard for me to trace what could be the issue for you, especially if no one was experiencing this before. Also this is a new issue thats just started to happen? have you updated anything else?

[cnaccio]

Hey man, thanks for the quick response. Yes, the issue was on page load. The problem appears intermittent, and clearing the browser cache/history resolves it temporary. Not sure if it's a new issue or not as it could of just not reared its ugly head until lately. That said, we have been using the components for a few months and have now just started hearing reports about the problem. Lastly, we haven't updated anything else.

We've added an issue to our backlog to upgrade Stike to v1.0, but would def prefer to avoid that if possible as everything is working right now except for this strange random error.

Let me know if there's any other information I can provide. Thanks brother!

On Tue, Jan 2, 2018 at 10:50 AM daneowens3 notifications@github.com wrote:

hello @cnaccio https://github.com/cnaccio this is happening on page load? being three versions back makes it a little hard for me to trace what could be the issue for you, especially if no one was experiencing this before. Also this is a new issue thats just started to happen? have you updated anything else?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/appiphony/Strike-Components/issues/175#issuecomment-354812710, or mute the thread https://github.com/notifications/unsubscribe-auth/AHq1N1Wz1swngoiEKwgR470Q49ItLkuqks5tGl5ygaJpZM4RPeYK .

--

Charles Naccio, Salesforce Consultant(Mobile) 214.305.8684 <214.305.8684> (Office) 877.778.3113 (Fax) 866.479.8373

• <214.305.8684>*

This communication and any documents, files, or previous e-mail messages attached to it constitute an electronic communication within the scope of the Electronic Communication Privacy Act, 18 USCA 2510. This communication may contain non-public, confidential, or legally privileged information intended for the sole use of the designated recipient(s). The unlawful interception, use or disclosure of such information is strictly prohibited under 18 USCA 2511 and any applicable laws.

[daneowens3]

still trying to figure out why this is happening and reproduce, but it could have been related to another bug we fixed in the past. So far i've been unsuccessful in recreating this error but will keep investigating.

[cnaccio]

Sounds good. Will let you know if I get any other details or if it goes away. Thanks man!

On Wed, Jan 3, 2018 at 10:31 AM daneowens3 notifications@github.com wrote:

still trying to figure out why this is happening and reproduce, but it could have been related to another bug we fixed in the past. So far i've been unsuccessful in recreating this error but will keep investigating.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/appiphony/Strike-Components/issues/175#issuecomment-355057384, or mute the thread https://github.com/notifications/unsubscribe-auth/AHq1N8U1znf7KeDH4omTJCF5e3Rr2yJ9ks5tG6tagaJpZM4RPeYK .

--

Charles Naccio, Salesforce Consultant(Mobile) 214.305.8684 <214.305.8684> (Office) 877.778.3113 (Fax) 866.479.8373

• <214.305.8684>*

This communication and any documents, files, or previous e-mail messages attached to it constitute an electronic communication within the scope of the Electronic Communication Privacy Act, 18 USCA 2510. This communication may contain non-public, confidential, or legally privileged information intended for the sole use of the designated recipient(s). The unlawful interception, use or disclosure of such information is strictly prohibited under 18 USCA 2511 and any applicable laws.