The Welkin Suite Forum

[Fixed] Can't open Lightning components



Can't open Lightning components

  • Please log in to reply

#1
windows version welkinsuite

funkyuzzi

    Posted 24 May 2017 and edited 06 Mar 2018

    With the new update I can't open any of the Lightning components in one of my projects. The project loads fine but when I try to open any of the files in any bundle I get an Object reference not set to instance of object. Other projects are fine so it's something about this one. 

    There are two errors in the log around the time of the error:

    2017/05/24 10:02:11.332 [WARN] [20] System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
    Parameter name: position
    at Microsoft.VisualStudio.Text.Implementation.BinaryStringRebuilder.GetLineNumberFromPosition(Int32 position)
    at Microsoft.VisualStudio.Text.Implementation.TextSnapshot.GetLineFromPosition(Int32 position)
    at WelkinSuite.ApexCodeAssistance.Implementation.Outlining.OutliningTagger.UpdateRegions()
    at WelkinSuite.ApexCodeAssistance.Implementation.Outlining.OutliningTagger.ReflectionChangedHandler(Object sender, ChangeMessage change)
    at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.Repository.ReflectionRepository.OnReflectionChanged(ChangeMessage e)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.Repository.ReflectionRepository.ProcessChange()
    System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
    Parameter name: position
    at Microsoft.VisualStudio.Text.Implementation.BinaryStringRebuilder.GetLineNumberFromPosition(Int32 position)
    at Microsoft.VisualStudio.Text.Implementation.TextSnapshot.GetLineFromPosition(Int32 position)
    at WelkinSuite.ApexCodeAssistance.Implementation.Outlining.OutliningTagger.UpdateRegions()
    at WelkinSuite.ApexCodeAssistance.Implementation.Outlining.OutliningTagger.ReflectionChangedHandler(Object sender, ChangeMessage change)
    at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.Repository.ReflectionRepository.OnReflectionChanged(ChangeMessage e)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.Repository.ReflectionRepository.ProcessChange()
    WelkinSuite.ApexCodeAnalyzers.Prospector.IdentitySource.EditorIdentitySource
    2017/05/24 10:20:17.299 [DEBUG] [19] WelkinSuite.ApexCodeAnalyzers.Prospector.AmbiguousReparseException: Ambiguous reparse exception.
    at WelkinSuite.ApexCodeAnalyzers.Prospector.ThoroughApexParser.BuildReflectionNode(ParserRuleContext ctx, Int32 offset, SyntaxItemType itemType)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.ThoroughApexParser.GetParsedDocument(ReadonlyInterval interval, SyntaxItemType type)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.ThoroughApexParser.GetParsedDocument(DirtyRegion region)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.IdentitySource.EditorIdentitySource.ProcessSeparatedRegions()
    at WelkinSuite.ApexCodeAnalyzers.Prospector.IdentitySource.EditorIdentitySource.DirtyRegionProcessor()
    WelkinSuite.ApexCodeAnalyzers.Prospector.AmbiguousReparseException: Ambiguous reparse exception.
    at WelkinSuite.ApexCodeAnalyzers.Prospector.ThoroughApexParser.BuildReflectionNode(ParserRuleContext ctx, Int32 offset, SyntaxItemType itemType)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.ThoroughApexParser.GetParsedDocument(ReadonlyInterval interval, SyntaxItemType type)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.ThoroughApexParser.GetParsedDocument(DirtyRegion region)
    at WelkinSuite.ApexCodeAnalyzers.Prospector.IdentitySource.EditorIdentitySource.ProcessSeparatedRegions()
    at WelkinSuite.ApexCodeAnalyzers.Prospector.IdentitySource.EditorIdentitySource.DirtyRegionProcessor()
    WelkinSuite.ApexCodeAnalyzers.Prospector.Repository.ReflectionRepository

    Nothing that seems directly relevant in the ActivityLog but there are some errors trying to load pieces of the VS shell:

    Microsoft.VisualStudio.Shell.TreeNavigation.GraphProvider.dll
    VsDebugPresentationPackage.dll

    Anyone else experiencing this?

    Uzzi



    5 replies to this topic

    #2

    kate.dulko

      Posted 25 May 2017

      Hi Uzzi,


      Thank you for your post.

      Also, we received your bug report with the attached log files. Our developers have investigated them, and I kindly ask you to answer the next questions which will help to understand the exact reason for your issue:

           1. Can you please check if the path of your lightning members which cannot be open is not too long? Especially this is related with *.cmp and *.app files in your local folder of TWS project. How many symbols are present in this path?

           2. Also, can you please check if there can be some specific symbols in the path of your *cmp and *.app files?

           3. Do your Lightning members have some suffixes in their names? For example, 'Render', 'Controller', or 'Helper'. 

           4. Does the issue apply for the project wich was created in the Bloom R1 version of the IDE or it is the project which you used previously?

           5. Are you trying to open the Lightning files from the Solution Explorer or from the Lightning Bundle Explorer? If you are working with Solution Explorer, can you please check if the same files are present in the Lightning Bundle Explorer? You can open the last one using the menu View -> Lightning Bundle Explorer.


      All this information will help us to solve the issue which you are faced with.


      Thank you greatly,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        


      #3

      funkyuzzi

        Posted 25 May 2017

        kate.dulko, on May 25, 2017 - 12:14 PM, said:

        Hi Kate,

        Thank you for your response. My answers are below.

             1. Can you please check if the path of your lightning members which cannot be open is not too long? Especially this is related with *.cmp and *.app files in your local folder of TWS project. How many symbols are present in this path?

        Uzzi: The longest path is about 150 characters and there are no symbols or special characters in the path. I also tried creating a new project in c:\temp (so a much shorter path) and it has the same problem.

             2. Also, can you please check if there can be some specific symbols in the path of your *cmp and *.app files?

        Uzzi: There are no symbols or special characters in the path or any of the file names.

             3. Do your Lightning members have some suffixes in their names? For example, 'Render', 'Controller', or 'Helper'. 

        Uzzi: One of them does, and you helped me realize that was a problem for the Lightning Bundle Explorer but the Solution Explorer still worked fine until the new release. I also tried removing the bundle that had "Helper" in the name, and creating a new project without that bundle (both in the same solution and in a brand new solution) but the problem remains.

             4. Does the issue apply for the project wich was created in the Bloom R1 version of the IDE or it is the project which you used previously?

        Uzzi: Both. I was using a solution and project created in an earlier version but today I created a new solution and project and populated it (without the *Helper component mentioned above) and that has the same problem.

             5. Are you trying to open the Lightning files from the Solution Explorer or from the Lightning Bundle Explorer? If you are working with Solution Explorer, can you please check if the same files are present in the Lightning Bundle Explorer? You can open the last one using the menu View -> Lightning Bundle Explorer.

        Uzzi: I get the object instance error trying to open from the Solution Explorer. If I try to open the Lightning Bundle Explorer the whole IDE crashes. 

         
        Thank you for your help on this. Going back to Dev Console is a nightmare after TWS! :)
         
        Uzzi



        #4

        kate.dulko

          Posted 26 May 2017

          Hi Uzzi,


          Thank you for your response.


          The reason for TWS crash when you open the Lightning Bundle Explorer is that the IDE cannot get members of one of your bundles. All of them exist in your TWS project and locally, however, TWS cannot combine correctly some files as members of one bundle to show the list, and as a result, the Lightning Bundle Explorer fails to open. 

          Also, this is the general reason for the error when you open lightning files using the Solution Explorer. According to the current implementation, the IDE appeals to the Lightning Bundle Explorer to get all the bundle's members to show them in the Lightning editor. Since the list in the Bundle Explorer cannot be initialized all other bundles and their members cannot be opened also.


          I kindly ask you to create a new project and download the Lightning Event, Interface, and Tokens Bundles only. Can you please tell me if you can open files from these bundles?

          After this, please add one of your Application or Components Bundle and check if its file can be opened. If no, may I please ask you to send us its name - you can send it via email. If files would be opened without error, please add another bundle and check its files. This way we will find the bundle which causes the issue in your TWS project.


          Thank you greatly for your collaboration in our investigation.

          We will release the fix for this issue as soon as we will find the reason and the way to solve it.


          Regards,

          Kate



          Kate Dulko
          Customer Relations

          The Welkin Suite

          twitter: @KateDulko
          skype id: d_katerina
          e-mail: kate.dulko@welkinsuite.com

           

            


          #5

          funkyuzzi

            Posted 26 May 2017

            Hi Kate,


            As I was working through your instructions I noticed that I had another component with "Controller" in the name. Once I removed that component from the project, everything started working again. Not sure how I missed that one the first time through - sorry about that!


            Thanks so much for your help!

            Uzzi



            #6

            kate.dulko

              Posted 26 May 2017

              Hi Uzzi,


              Thank you for your response with the update!

              I'm glad that now you can continue your working process in The Welkin Suite IDE without switching to Dev Console.


              Our developers have already solved this issue and this fix will be included to the next version of the IDE, and you will be able to add these files to our TWS project.


              Best Regards,

              Kate


              Kate Dulko
              Customer Relations

              The Welkin Suite

              twitter: @KateDulko
              skype id: d_katerina
              e-mail: kate.dulko@welkinsuite.com

               

                


              Boost Your Productivity. Get Started Today

              Try Free Trial