[SalesForce] Lightning Component not showing in Community App Builder

I have a component that is not showing on Community Builder.My managed package app has a component and one of our customers has an issue where we cannot see the Lightning Component in the Community Builder >> Custom Components. I am wondering if that could be permission?

Here are the things that I have verified.

1 – In the component I have set forceCommunity:availableForAllPageTypes.

<aura:component implements="forceCommunity:availableForAllPageTypes" access="global" controller="XXXComponentController" >

2 – The Customer has deployed the Domain to users.

3 – We can see other components on Community Builder >> Custom Components(Those components are all created manually not from managed package).

4 – If I install the same app version in a new org, I can see the component.

My questions are:
1 – Is there any Permission Set that I need to set?
2 – Is there anything else I could check?
3 – If I enable the Debug mode, which information I should look for in the console?

Thank you in advance!

Best Answer

I created a new version and I pushed to the customer again, and seems to solve the issue, somehow it shows the component in his org. Thank you for all the answers.

Updated on: 2019-09-27
Another way to solve this issue is to compile all the Apex classes.

Related Solutions

[SalesForce] Can we use managed lightning component in lightning application

You can use managed lightning component in other lightning app.

There is an attribute named access which needs to be set. For ex:

<aura:component access="global" controller="KendoController" implements="forceCommunity:availableForAllPageTypes,force:appHostable,flexipage:availableForAllPageTypes,force:hasRecordId">

[SalesForce] Lightning Community via custom Mobile SDK app

Your approach of a 'simple Hybrid App that sends you to the Community Login page' is the right path here.

As for your other concerns

but I'm concerned that Locker Service will cause a problem with the Cordova integration layer.

You'll essentially be building what's a remote-hybrid app so the community would be loaded in a WebView container. Based on what I've seen, Locker Service does not cause any issues in such a case.

Besides wanting to provide a branded app, we will like also need to support Push Notifications

Push notifications are only supported for native apps and hybrid-local apps. It will NOT work for hybrid-remote app if you use the approach mentioned above. The root cause is the same - you are essentially running your app in a webview container.

and to allow document uploads via the device's camera.

This will work but you'll need to handle it inside your Apex/ VF/ JS code (remember it loads in a WebView)

Can this be done in a Mobile SDK app that wraps a Lightning Community Builder community? Any special caveats? I'd like to be sure we are considering all possible issues during design, before we begin building.

These are valid and important architectural concerns to build at this stage. In addition to the above, you might want to consider

Performance - Hybrid-remote apps aren't the best in terms of performance as you're essentially limited to a web view and not leveraging the device performance except for a webview.
Code reuse - I understand one of the big factors in chosing this approach would be just to mobilise your existing Lightning Community without the need for building additional mobile apps
Hardware Features - Accessing hardware via remote apps is not always optimal as you're not essentially leveraging the capabilities via a bridge.

Related Topic